Systems and methods for traffic load balancing on multiple wan backhauls and multiple distinct lan networks

ABSTRACT

In accordance with embodiments disclosed herein, there are provided methods, systems, mechanisms, techniques, and apparatuses for traffic aggregation on multiple Wide Area Network (WAN) backhauls and multiple distinct Local Area Network (LAN) networks; for traffic load balancing on multiple WAN backhauls and multiple distinct LAN networks; and for performing self-healing operations utilizing multiple WAN backhauls serving multiple distinct LAN networks. For example, in one embodiment, a first Local Area Network LAN access device is to establish a first LAN; a second LAN access device is to establish a second LAN; a first Wide Area Network WAN backhaul connection is to provide the first LAN access device with WAN connectivity; a second WAN backhaul connection to provide the second LAN access device with WAN connectivity; a management device is communicatively interfaced with each of the first LAN access device, the second LAN access device, the first WAN backhaul connection, and the second WAN backhaul connection; and the management device routes a first portion of traffic originating from the first LAN over the first WAN backhaul connection and routes a second portion of the traffic originating from the first LAN over the second WAN backhaul connection.

CROSS REFERENCE TO RELATED APPLICATIONS

The present application is a continuation of and claims priority benefitunder 35 U.S.C. § 120, to co-pending U.S. patent application Ser. No.14/362,585, entitled “Systems and Methods for Traffic Load Balancing onMultiple WAN Backhauls and Multiple Distinct LAN Networks,” naming asinventors Peter Chow, Ramya Bhagavatula, Wongjong Rhee, Ardavan MalekiTehrani, John Cioffi, Stefano Galli, Sungho Yun, Kenneth Kerpez and MarcGoldburg, and filed Jun. 3, 2014, which claims priority to InternationalPCT Patent Application No. PCT/US11/63327, entitled “Systems and Methodsfor Traffic Load Balancing on Multiple WAN Backhauls and MultipleDistinct LAN Networks,” and filed Dec. 5, 2011. Each reference mentionedin this patent document is hereby incorporated herein by reference inits entirety.

A. TECHNICAL FIELD

The subject matter described herein relates generally to the field ofcomputing, and more particularly, to systems and methods for trafficaggregation on multiple WAN backhauls and multiple distinct LANnetworks; to systems and methods for traffic load balancing on multipleWAN backhauls and multiple distinct LAN networks; and to systems andmethods for performing self-healing operations utilizing multiple WANbackhauls serving multiple distinct LAN networks.

B. DESCRIPTION OF THE RELATED ART

The subject matter discussed in the background section should not beassumed to be prior art merely as a result of its mention in thebackground section. Similarly, a problem mentioned in the backgroundsection or associated with the subject matter of the background sectionshould not be assumed to have been previously recognized in the priorart. The subject matter in the background section merely representsdifferent approaches, which in and of themselves may also correspond toembodiments of the claimed subject matter.

The “Internet” is a Wide Area Network that joins together many othernetworks, providing a communications path between devices operatingwithin distinct and often geographically dispersed networks. A LocalArea Network (LAN) enables multiple distinct devices within anend-user's premises to communicate amongst themselves locally. Home LANtechnologies include wired Ethernet, WiFi, power line, coax, phonelineand other transmission systems. An end-user's LAN is often connected tothe Internet via a WAN backhaul connection to an Internet ServiceProvider (ISP) that provides the end-user consumer with Internetconnectivity and Internet Bandwidth. WAN backhaul technologies includeDSL, cable modems, fiber, and wireless. Devices within the end-user'sLAN may communicate with devices external to the LAN over the WANbackhaul connection provided by the end-user's ISP.

Traditionally, the WAN is controlled, managed and maintained by serviceproviders, such as Internet Service Providers, TelecommunicationsOperators, etc. Conversely, a LAN is typically managed and maintained ata customer's premises by end users/customers, which may be residentialusers or commercial/business customers. Moreover, operators and serviceproviders typically refrain from addressing any LAN related problems,notwithstanding the fact that, at times, some problems and issuesexhibited via the LAN may be related to WAN configurations and settings.Opportunities for enhanced management of the LAN to WAN interfaces maybenefit LANs, LAN devices, and end-to-end service delivery. However,such enhanced management opportunities have not yet been made availableto the relevant consuming public and have not yet been explored inearnest by relevant Service Providers.

The present state of the art may therefore benefit from systems andmethods for traffic aggregation on multiple WAN backhauls and multipledistinct LAN networks; systems and methods for traffic load balancing onmultiple WAN backhauls and multiple distinct LAN networks; and systemsand methods for performing self-healing operations utilizing multipleWAN backhauls serving multiple distinct LAN networks, each of which aredescribed herein.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments are illustrated by way of example, and not by way oflimitation, and will be more fully understood with reference to thefollowing detailed description when considered in connection with thefigures in which:

FIG. 1 illustrates an exemplary architecture in which embodiments mayoperate;

FIGS. 2A, 2B, 2C, 2D, 2E, 2F, 2G, and 2H illustrate alternativeexemplary architectures in which embodiments may operate;

FIGS. 3A, 3B, 3C, 3D, and 3E illustrate alternative exemplaryarchitectures in which embodiments may operate;

FIGS. 4A, 4B, 4C, 4D, 4E, 4F, and 4G illustrate alternative exemplaryarchitectures in which embodiments may operate;

FIGS. 5A and 5B show diagrammatic representations of systems inaccordance with which embodiments may operate, be installed, integrated,or configured;

FIGS. 6A, 6B, and 6C are flow diagrams illustrating methods for trafficaggregation; methods for traffic load balancing; and methods forperforming self-healing in accordance with described embodiments; and

FIG. 7 illustrates a diagrammatic representation of a machine in theexemplary form of a computer system, in accordance with one embodiment.

DETAILED DESCRIPTION

Described herein are systems and methods for traffic aggregation onmultiple WAN backhauls and multiple distinct LAN networks; systems andmethods for traffic load balancing on multiple WAN backhauls andmultiple distinct LAN networks; and systems and methods for performingself-healing operations utilizing multiple WAN backhauls servingmultiple distinct LAN networks.

Demand for data traffic is bursty, with frequent large changes intraffic. Demand for streaming services such as video can also varysubstantially as sessions come and go, such as when turning a TV on andoff. Moreover, the supply of bandwidth can vary considerably, withdifferent LAN connections such as wireless proving different bit rates,and different WAN connections such as broadband access backhaul alsoproviding different bit rates. It is often the case that when one lineis heavily loaded, an adjacent line is lightly loaded. Trafficaggregation takes advantage of this, statistically smoothing demand andsupply by pooling multiple users together into a single logicallycreated connection.

LAN/WAN bonding solutions heretofore have been limited to specificpre-determined implementations. The traffic aggregation mechanismsdisclosed herein are more dynamic in nature and allow for combiningtraffic across different WAN backhauls and LAN networks in an adaptivefashion. Traffic aggregation might include, among other things,techniques such as packet reordering, classification by packet type(control or data), etc. Traffic can also be aggregated across devices indifferent subnets, networks being serviced by different serviceproviders, etc. Certain traffic aggregation mechanisms do notdifferentiate incoming traffic on the basis of traffic flows, so thatresources are allocated to the whole set of flows. There are alsotraffic aggregation mechanisms that do not treat all incoming traffic asthe same and each flow can be allocated its own dedicated resources. Anytraffic handling scheme presents different requirements in terms of linkcapacity and also has its own sensitivity to changes in the traffic loadoffered to the network. This interdependency between the performance oftraffic aggregation schemes and link status (capacity, offered load,flow characteristics, etc.) is present regardless of whether aggregationis performed by aggregating traffic over a single connection or byswitching or routing physically or logically distinct traffic sourcesand sinks over different connections, and in both cases requires toadapt configuration to the specific scenario at hand. Trafficaggregation is thus more adaptive and may be adapted to suit thesituation at hand where as bonding tends to be more static.

For example, in one embodiment, a first Local Area Network (LAN) accessdevice is to establish a first LAN; a second LAN access device is toestablish a second LAN; a first Wide Area Network (WAN) backhaulconnection is to provide the first LAN access device with WANconnectivity; a second WAN backhaul connection is to provide the secondLAN access device with WAN connectivity; and a traffic aggregation unitis to form a logically bonded WAN interface over the first WAN backhauland the second WAN backhaul. In some embodiments an optional trafficde-aggregation unit may be used.

In another embodiment, a first Local Area Network (LAN) access device isto establish a first LAN; a second LAN access device is to establish asecond LAN; a first Wide Area Network (WAN) backhaul connection is toprovide the first LAN access device with WAN connectivity; a second WANbackhaul connection to provide the second LAN access device with WANconnectivity; a management device is communicatively interfaced witheach of the first LAN access device, the second LAN access device, thefirst WAN backhaul connection, and the second WAN backhaul connection;and the management device routes a first portion of traffic originatingfrom the first LAN over the first WAN backhaul connection and routes asecond portion of the traffic originating from the first LAN over thesecond WAN backhaul connection.

In another embodiment, a first Local Area Network (LAN) access device isto establish a first LAN; a second LAN access device is to establish asecond LAN; a first Wide Area Network (WAN) backhaul connection is toprovide the first LAN access device with WAN connectivity; a second WANbackhaul connection is to provide the second LAN access device with WANconnectivity; a management device is communicatively interfaced witheach of the first LAN access device, the second LAN access device, thefirst WAN backhaul connection, and the second WAN backhaul connection;and the management device, responsive to a failure event, re-routestraffic associated with the first LAN onto the second WAN backhaulconnection or re-routes traffic associated with the second LAN onto thefirst WAN backhaul connection.

In accordance with embodiments described herein, end-user consumers,including residential consumers and business consumers, may connect tothe Internet by way of a Wide Area Network (WAN) backhaul connection toa Service Provider (SP), such as an Internet Service Provider (ISP), orto a Service Provider that provides one or more of data connectivity,voice connectivity, video connectivity, and mobile device connectivityto a plurality of subscribers. Such Service Providers may include aDigital Subscriber Line (DSL) internet service provider which providesits subscribing end-users with Internet bandwidth at least partiallyover copper twisted pair telephone lines, such as that conventionallyutilized to carry analog telephone service (e.g., Plain Old TelephoneService (POTS); a coaxial cable internet service provider which providesend-users with Internet bandwidth at least partially over coaxial cable,such as that conventionally utilized to carry “cable” televisionsignals; or a fiber optics internet service provider which providesend-users with Internet bandwidth at over fiber optic cable thatterminates at a customer's premises. Other variants exist as well, suchas ISPs which provide Internet bandwidth as an analog signal over ananalog telephone based connection, ISPs that provide Internet bandwidthover a one-way or two-way satellite connection, and ISPs that provideInternet bandwidth at least partially over power lines, such as powerlines conventionally utilized to transmit utility power (e.g.,electricity) to an end-user's premises, or ISPs that provide Internetbandwidth at least partially over wireless channels, such as wireless(e.g., WiFi) connectivity at hotspots, or mobile data connectivity viatechnologies and standards such as WiMax, 3G/4G, LTE, etc.

At an end-user's premises, Internet bandwidth and other compatibleservices provided via a WAN backhaul connection to an ISP is commonlydistributed amongst multiple devices within the end-user's premises viaa Local Area Network (LAN), which may be established via a LAN device.Distribution of the Internet Bandwidth and other services provided viathe WAN backhaul may further extend to an area around an end-user'spremises, such as to an area outside a home, to a space or area outsideof or around a business in which the Internet Bandwidth is accessiblevia the end-user's LAN wirelessly. At the end-user's premises, networktraffic may be distributed within the LAN via wired connections orwireless connections, for example, over coaxial wiring, electrical powerwiring, twisted-pair telephone wiring, variants of Ethernet/Category-5type wiring, and various types of wireless radio signals using licensedand unlicensed spectrum and various protocols. In accordance with oneembodiment, access to Internet bandwidth and other services provided bythe WAN backhaul may be secured.

Some network traffic associated with the end-user's premises remainslocal to the LAN, while other traffic destined for locations external tothe LAN traverse the LAN onto the WAN interface and onto the Internetvia the WAN backhaul.

Besides network traffic traversing the WAN and LAN networks andinterfaces, various types of information is available, retrievable, orobservable from each of the distinct WAN and LAN networks. Themanagement device described herein may collect information collectedfrom the WAN and LAN networks via respective WAN and LAN interfaces tosuch networks, and perform or enable various enhancements, such asperforming self-healing operations utilizing multiple WAN backhaulsserving multiple distinct LAN networks; and load balancing trafficutilizing multiple WAN backhauls serving multiple distinct LAN networks.The management device may further coordinate or instruct the formationof a logical WAN backhaul connection over multiple underlying physicalor wireless WAN backhauls. Some embodiments make use of a trafficaggregation unit which may form a logically bonded WAN interface fromtwo or more underlying WAN interfaces. In some embodiments, a trafficde-aggregation unit may optionally be employed. Traffic aggregation mayuse inverse multiplexing, Ethernet switching, IP routing, AsynchronousTransfer Mode (ATM), Time-Division Multiplexing (TDM), Point-to-PointProtocol (PPP), PPP Multi-Link Protocol (MLPPP), or other technologies.

An alternative to classic traffic aggregation is to selectivelyaggregate traffic by switching or routing physically or logicallydistinct traffic sources and sinks over different connections. Forexample, traffic from a first subnet on a LAN can travel over a firstWAN connection, while traffic from a second subnet on a LAN can travelover a second WAN connection. This selective aggregation mechanism canswitch or route traffic according to physical port, priority level,Ethernet VLAN or MAC identities, IP number, subnet, TCP/UDP port number,protocol, type of service (TOS), DiffSery Code Point (DSCP), IPprecedence, MPLS tag, application layer, etc.

Aggregation via selectively switching or routing traffic may beperformed with no physical aggregation element, for example, anaggregation element may be either physical entity or a logically definedentity in accordance with the various described embodiments.

Aggregation and selection of connections may be varied adaptively, astraffic demands and connection bandwidths change over time. For example,a high traffic demand from a first LAN may be routed over both a firstand a second WAN, but when the traffic demand from the first LANdecreases the traffic ceases to be routed over the second WAN. Iftraffic demand increases on the second LAN such traffic may then berouted over the first WAN. More involved real-time load balancing may beincorporated to match overall traffic demands with bandwidth supply inan adaptive fashion.

Disclosed embodiments may also be extended to cases with more than twoLANs or more than two WAN connections. In such cases, trafficaggregation schemes have multiple traffic inputs and multiple choices onhow to aggregate traffic, for example, over a single connection ormultiple connections each with its own link quality, capacity. Sincethere is interdependency between the performances of traffic aggregationschemes and input flow characteristics and link quality, traffic can beaggregated taking a weighted approach to better serve the scenario athand. Traffic can be weighted to account for the fact that not allaccess point conditions are equal, therefore when connections are madeto more than two access points, the connections to different accesspoints may be weighted accordingly, for example, to compensate for thedifferent speeds, throughput, latency, or other characteristicsassociated with the distinct access points. In one embodiment, weightingis dependent upon the supply of bandwidth on the different WANconnections, and further dependent upon the traffic demand from thedifferent LANs. The weighting may further vary with the type or priorityof traffic, different service levels, different services, etc. Theweighting may also be time varying as a consequence of the fact thatchannel quality also changes over time. This applies also the LAN casewhere it is well known that in-home power line communications (PLC)faces time varying impairments.

Disclosed embodiments may also be extended to cases where the same LANextends over multiple physically separated channels. For example, suchas the case of having a LAN where G.hn (ITU-T standardized unifiedhigh-speed wire-line based home networking) nodes operate overphoneline, power lines, and coax; or in the case of a hybridwireline/wireless LAN. In cases, traffic aggregation over the WAN mayapply different weights on input flows originating on coax or phonelineor power line or wireless. Similarly, when one source requires so manychannel resources that no single physical channel is able to satisfythem, then traffic handling schemes may split the input traffic andsimultaneously transmit the input traffic over multiple channels. Thiscan be accomplished using possibly unequal weights depending on linkconditions and then re-aggregate the input traffic over the WAN oreventually at the sink within the LAN. The way in which incoming trafficis simultaneously transmitted over multiple channels can change overtime with link condition and traffic requirements.

In the following description, numerous specific details are set forthsuch as examples of specific systems, languages, components, etc., inorder to provide a thorough understanding of the various embodiments. Itwill be apparent, however, to one skilled in the art that these specificdetails need not be employed to practice the disclosed embodiments. Inother instances, well known materials or methods have not been describedin detail in order to avoid unnecessarily obscuring the disclosedembodiments.

In addition to various hardware components depicted in the figures anddescribed herein, embodiments further include various operations whichare described below. The operations described in accordance with suchembodiments may be performed by hardware components or may be embodiedin machine-executable instructions, which may be used to cause ageneral-purpose or special-purpose processor programmed with theinstructions to perform the operations. Alternatively, the operationsmay be performed by a combination of hardware and software, includingsoftware instructions that perform the operations described herein viamemory and one or more processors of a computing platform.

Embodiments also relate to a system or apparatus for performing theoperations herein. The disclosed system or apparatus may be speciallyconstructed for the required purposes, or it may comprise a generalpurpose computer selectively activated or reconfigured by a computerprogram stored in the computer. Such a computer program may be stored ina non-transitory computer readable storage medium, such as, but notlimited to, any type of disk including floppy disks, optical disks,flash, NAND, solid state drives (SSDs), CD-ROMs, and magnetic-opticaldisks, read-only memories (ROMs), random access memories (RAMs), EPROMs,EEPROMs, magnetic or optical cards, or any type of media suitable forstoring non-transitory electronic instructions, each coupled to acomputer system bus. In one embodiment, a non-transitory computerreadable storage medium having instructions stored thereon, causes oneor more processors within a Management Device, a traffic aggregationunit, and/or a traffic de-aggregator to perform the methods andoperations which are described herein. In another embodiment, theinstructions to perform such methods and operations are stored upon anon-transitory computer readable medium for later execution.

The algorithms and displays presented herein are not inherently relatedto any particular computer or other apparatus nor are embodimentsdescribed with reference to any particular programming language. It willbe appreciated that a variety of programming languages may be used toimplement the teachings of the embodiments as described herein.

FIG. 1 illustrates an exemplary architecture 100 in which embodimentsmay operate. Asymmetric Digital Subscriber Line (ADSL) systems (one formof Digital Subscriber Line (DSL) systems), which may or may not includesplitters, operate in compliance with the various applicable standardssuch as ADSL1 (G.992.1), ADSL-Lite (G.992.2), ADSL2 (G.992.3),ADSL2-Lite G.992.4, ADSL2+ (G.992.5) and the G.993.x emergingVery-high-speed Digital Subscriber Line or Very-high-bitrate DigitalSubscriber Line (VDSL) standards, as well as the G.991.1 and G.991.2Single-Pair High-speed Digital Subscriber Line (SHDSL) standards, allwith and without bonding, and/or the G.997.1 standard (also known asG.ploam).

In performing the disclosed functions, systems may utilize a variety ofoperational data (which includes performance data) that is available atan Access Node (AN).

In FIG. 1, users terminal equipment 102 (e.g., a Customer PremisesEquipment (CPE) device or a remote terminal device, network node, LANdevice, etc.) is coupled to a home network 104, which in turn is coupledto a Network Termination (NT) Unit 108. DSL Transceiver Units (TU) arefurther depicted (e.g., a device that provides modulation on a DSL loopor line). In one embodiment, NT unit 108 includes a TU-R (TU Remote),122 (for example, a transceiver defined by one of the ADSL or VDSLstandards) or any other suitable network termination modem, transceiveror other communication unit. NT unit 108 also includes a ManagementEntity (ME) 124. Management Entity 124 can be any suitable hardwaredevice, such as a microprocessor, microcontroller, or circuit statemachine in firmware or hardware, capable of performing as required byany applicable standards and/or other criteria. Management Entity 124collects and stores, among other things, operational data in itsManagement Information Base (MIB), which is a database of informationmaintained by each ME capable of being accessed via network managementprotocols such as Simple Network Management Protocol (SNMP), anadministration protocol used to gather information from a network deviceto provide to an administrator console/program or via TransactionLanguage 1 (TL1) commands, TL1 being a long-established command languageused to program responses and commands between telecommunication networkelements. In one embodiment, Network Termination Unit 108 iscommunicably interfaced with a management device 170 as describedherein. In another embodiment, TU-R 122 is communicably interfaced withmanagement device 170.

Each TU-R 122 in a system may be coupled with an TU-C (TU Central) in aCentral Office (CO) or other central location. TU-C 142 is located at anAccess Node (AN) 114 in Central Office 146. A Management Entity 144likewise maintains an MIB of operational data pertaining to TU-C 142.The Access Node 114 may be coupled to a broadband network 106 or othernetwork, as will be appreciated by those skilled in the art. TU-R 122and TU-C 142 are coupled together by a loop 112, which in the case ofADSL may be a twisted pair line, such as a telephone line, which maycarry other communication services besides DSL based communications.Either management entity 124 or management entity 144 may implement andincorporate a management device 170 as described herein. Managemententity 124 or management entity 144 may further store collected WANinformation and collected LAN information within an associated MIB.

Several of the interfaces shown in FIG. 1 are used for determining andcollecting operational data. The Q interface 126 provides the interfacebetween the Network Management System (NMS) 116 of the operator and ME144 in Access Node 114. Parameters specified in the G.997.1 standardapply at the Q interface 126. The near-end parameters supported inManagement Entity 144 may be derived from TU-C 142, while far-endparameters from TU-R 122 may be derived by either of two interfaces overthe UA interface. Indicator bits and EOC messages may be sent usingembedded channel 132 and provided at the Physical Medium Dependent (PMD)layer, and may be used to generate the required TU-R 122 parameters inME 144. Alternately, the operations, Administration and Maintenance(OAM) channel and a suitable protocol may be used to retrieve theparameters from TU-R 122 when requested by Management Entity 144.Similarly, the far-end parameters from TU-C 142 may be derived by eitherof two interfaces over the U-interface. Indicator bits and EOC messageprovided at the PMD layer may be used to generate the required TU-C 142parameters in Management Entity 124 of NT unit 108. Alternately, the OAMchannel and a suitable protocol may be used to retrieve the parametersfrom TU-C 142 when requested by Management Entity 124.

At the U interface (also referred to as loop 112), there are twomanagement interfaces, one at TU-C 142 (the U-C interface 157) and oneat TU-R 122 (the U-R interface 158). Interface 157 provides TU-Cnear-end parameters for TU-R 122 to retrieve over the U interface/loop112. Similarly, U-R interface 158 provides TU-R near-end parameters forTU-C 142 to retrieve over the U interface/loop 112. The parameters thatapply may be dependent upon the transceiver standard being used (forexample, G.992.1 or G.992.2). The G.997.1 standard specifies an optionalOperation, Administration, and Maintenance (OAM) communication channelacross the U interface. If this channel is implemented, TU-C and TU-Rpairs may use it for transporting physical layer OAM messages. Thus, theTU transceivers 122 and 142 of such a system share various operationaldata maintained in their respective MIBs.

Depicted within FIG. 1 is management device 170 operating at variousoptional locations in accordance with several alternative embodiments.For example, management device 170 is located within home network 104,such as within a LAN. In an alternative embodiment, management device170 is located at central office 146 and interfaced to home network 104(e.g., a LAN) and broadband network 106 (e.g., a WAN) via NMS 116. Inyet another embodiment, management device 170 operates on the broadbandnetwork 106 (e.g., on the WAN or Internet).

Also depicted within FIG. 1 is a traffic aggregation unit 180 operatingat various optional locations in accordance with several embodiments.For example, traffic aggregation unit 180 may reside within TE 102, mayreside within a LAN device 103 which is connected with TE 102, trafficaggregation unit 180 may recite on the loop 112 at the CPE or CO side.As depicted here, traffic aggregation unit 180 is placed on the loop 112at NT 108. These and other examples and their benefits and function willbe described in further detail below.

As used herein, the terms “user,” “subscriber,” and/or “customer” referto a person, business and/or organization to which communicationservices and/or equipment are and/or may potentially be provided by anyof a variety of service provider(s). Further, the term “customerpremises” refers to the location to which communication services arebeing provided by a service provider. For an example Public SwitchedTelephone Network (PSTN) used to provide DSL services, customer premisesare located at, near and/or are associated with the network termination(NT) side of the telephone lines. Example customer premises include aresidence or an office building.

As used herein, the term “service provider” refers to any of a varietyof entities that provide, sell, provision, troubleshoot and/or maintaincommunication services and/or communication equipment. Example serviceproviders include a telephone operating company, a cable operatingcompany, a wireless operating company, an internet service provider, orany service that may independently or in conjunction with a broadbandcommunications service provider offer services that diagnose or improvebroadband communications services (DSL, DSL services, cable, etc.).

Additionally, as used herein, the term “DSL” refers to any of a varietyand/or variant of DSL technology such as, for example, Asymmetric DSL(ADSL), High-speed DSL (HDSL), Symmetric DSL (SDSL), and/or Veryhigh-speed/Very high-bit-rate DSL (VDSL). Such DSL technologies arecommonly implemented in accordance with an applicable standard such as,for example, the International Telecommunications Union (I.T.U.)standard G.992.1 (a.k.a. G.dmt) for ADSL modems, the I.T.U. standardG.992.3 (a.k.a. G.dmt.bis, or G.adsl2) for ADSL2 modems, I.T.U. standardG.992.5 (a.k.a. G.adsl2plus) for ADSL2+ modems, I.T.U. standard G.993.1(a.k.a. G.vdsl) for VDSL modems, I.T.U. standard G.993.2 for VDSL2modems, I.T.U. standard G.994.1 (G.hs) for modems implementinghandshake, and/or the I.T.U. G.997.1 (a.k.a. G.ploam) standard formanagement of DSL modems.

References to connecting a DSL modem and/or a DSL communication serviceto a customer are made with respect to exemplary Digital Subscriber Line(DSL) equipment, DSL services, DSL systems and/or the use of ordinarytwisted-pair copper telephone lines for distribution of DSL services, itshould be understood that the disclosed methods and apparatus tocharacterize and/or test a transmission medium for communication systemsdisclosed herein may be applied to many other types and/or variety ofcommunication equipment, services, technologies and/or systems. Forexample, other types of systems include wireless distribution systems,wired or cable distribution systems, coaxial cable distribution systems,Ultra High Frequency (UHF)/Very High Frequency (VHF) radio frequencysystems, satellite or other extra-terrestrial systems, cellulardistribution systems, broadband power-line systems and/or fiber opticnetworks. Additionally, combinations of these devices, systems and/ornetworks may also be used. For example, a combination of twisted-pairand coaxial cable interfaced via a balun connector, or any otherphysical-channel-continuing combination such as an analog fiber tocopper connection with linear optical-to-electrical connection at anOptical Network Unit (ONU) may be used.

The phrases “coupled to,” “coupled with,” connected to,” “connectedwith” and the like are used herein to describe a connection between twoelements and/or components and are intended to mean coupled/connectedeither directly together, or indirectly, for example via one or moreintervening elements or via a wired/wireless connection. References to a“communication system” are intended, where applicable, to includereference to any other type of data transmission system.

FIG. 2A illustrates an alternative exemplary architecture 200 in whichembodiments may operate. FIG. 2A depicts a first Wide Area Network (WAN)at element 205A, a second WAN 205B, a first Local Area Network (LAN) atelement 210A, and a second LAN 210B. LAN access device 220A connects LAN210A with WAN 205A through traffic aggregation unit 225. LAN 210B isconnected with WAN 205B through LAN access device 220B. LAN accessdevice 230 provides a communications interface between trafficaggregation unit 225 and LAN access device 220B.

In the series of exemplary embodiments set forth at FIGS. 2A through 2Hthere are two LAN access devices shown (e.g., 220A and 220B of FIG. 2A).However, more than two LAN access devices may permissible operate inaccordance with the described embodiments and the depiction of two suchLAN access devices in the exemplary figures is not to be construed asbeing limited to only two.

In accordance with one embodiment, such an architecture 200 or systemincludes a first Local Area Network (LAN) access device 220A toestablish a first LAN 210A and a second LAN access device 220B toestablish a second LAN 210B which is operationally distinct from thefirst LAN 210A. In such an embodiment, the architecture 200 or systemfurther includes a first Wide Area Network (WAN) backhaul connection 211to provide the first LAN access device 220A with WAN connectivity. Inthis embodiment, the architecture 200 or system further includes asecond WAN backhaul connection 212 to provide the second LAN accessdevice 210A with WAN connectivity. In this embodiment, each of the firstWAN backhaul connection 211 and the second WAN backhaul connection 212are physically distinct. The architecture 200 or system of thisembodiment further includes traffic aggregation unit 225 to form alogically bonded WAN interface 213 over the first WAN backhaulconnection 211 and the second WAN backhaul connection 212.

In one embodiment, the logically bonded WAN interface 213 provides thefirst LAN access device 220A and the second LAN access device 220B withWAN connectivity via a combination of first bandwidth accessible via thefirst WAN backhaul connection 211 and second bandwidth accessible viathe second WAN backhaul connection 212.

In one embodiment, the logically bonded WAN interface 213 provides thefirst LAN access device 220A with WAN connectivity and further providesthe second LAN access device 220B with WAN connectivity. In such anembodiment, the logically bonded WAN interface 213 supplants (e.g., isused in place of, replaces, supersedes, etc.) the first WAN backhaulconnection 211 for providing the first LAN access device 220A with itsrespective WAN connectivity and further supplants the second WANbackhaul connection 212 for providing the second LAN access device 220Bwith its respective WAN connectivity. For example, in such anembodiment, both LAN access devices 220A-B communicate via logicallybonded WAN interface 213 once established, rather than their respectiveWAN interfaces 211 and 212 respectively.

In one embodiment, the first WAN backhaul connection 211 provides thefirst LAN access device 220A with WAN connectivity via the first WANbackhaul connection 211 to a Service Provider that provides one or moreof data connectivity, voice connectivity, video connectivity, and mobiledevice connectivity to a plurality of subscribers. In one embodiment,the second WAN backhaul connection 212 provides the second LAN accessdevice 220B with WAN connectivity via the second WAN backhaul connection212 to the same Service Provider via a physically distinctcommunications link to the same Service Provider. For example, WANbackhaul connections 211 and 212 may represent physically distinctcommunications links, yet both communicably link to the same serviceprovider. Such a service provider may implement or establish the WideArea Networks 205A-B.

In one embodiment, the physically distinct communications link to thesame Service Provider associated with the second WAN backhaul connectionis identified by an Internet Protocol (IP) address distinct from an IPaddress for the first WAN backhaul connection. In such an embodiment,the physically distinct communications link to the same Service Providerassociated with the second WAN backhaul connection 212 is associatedwith a subscriber's account distinct from a subscriber's accountassociated with the first WAN backhaul connection 211. For example, thefirst WAN backhaul connection 211 may lead to one house or office, andthe second WAN backhaul connection 212 may lead to a separate anddistinct house or office. Nevertheless, both may trace back to the sameservice provider.

In one embodiment, the first WAN backhaul connection 211 provides thefirst LAN access device 220A with WAN connectivity via the first WANbackhaul connection 211 to a first Service Provider that provides one ormore of data connectivity, voice connectivity, video connectivity, andmobile device connectivity to a plurality of subscribers and the secondWAN backhaul connection 212 provides the second LAN access device 220Bwith WAN connectivity via the second WAN backhaul connection 212 to asecond Service Provider separate and distinct from the first ServiceProvider. For example, different from the preceding example, each of thefirst and second WAN backhaul connections 211 and 212 may lead tocompletely different service providers.

In one embodiment, at least a portion of traffic originating from thefirst LAN 210A and at least a portion of traffic originating from thesecond LAN 210B traverses the logically bonded WAN interface 213.

In one embodiment: (a) a first plurality of traffic packets originatingfrom the first LAN 210A traverses the logically bonded WAN interface 213via the first WAN backhaul 211 through the traffic aggregation unit 225;(b) a second plurality of traffic packets originating from the first LAN210A traverses the logically bonded WAN interface 213 via the second WANbackhaul 212 through the traffic aggregation unit 225; (c) a thirdplurality of traffic packets originating from the second LAN 210Btraverses the logically bonded WAN interface 213 via the first WANbackhaul 211 through the traffic aggregation unit 225; and (d) a fourthplurality of traffic packets originating from the second LAN 210Btraverses the logically bonded WAN interface 213 via the second WANbackhaul 212 through the traffic aggregation unit 225. Thus, packetsoriginating from either LAN 210A-B may traverse the logically bonded WANinterface 213 via either or both underlying WAN backhaul connection 211and/or 212. In such an embodiment, LAN devices within either LAN 210A-Bmay operate wholly agnostic or ignorant of which underlying backhaulconnection is being utilized for any given packet, as the trafficaggregation unit 225 provides the necessary coordination for theplurality of packets sent to, or designated for, various locationsaccessible within the WANs 205A-B (e.g., such as packets which must berouted to a location over the Internet, etc.).

In one embodiment, the first LAN 210A includes a first plurality ofinterconnected LAN nodes 238. In such an embodiment, each of the firstplurality of interconnected LAN nodes 238 are identifiable within thefirst LAN 210A by a private Internet Protocol (IP) address managed bythe first LAN access device 220A. In such an embodiment, the second LAN210B includes a second plurality of interconnected LAN nodes 239, inwhich each of the second plurality of interconnected LAN nodes 239 areidentifiable within the second LAN 210B by a private IP address managedby the second LAN access device 220B. In such an embodiment, the firstLAN access device 220A is identifiable via a first unique Public IPaddress assigned to the first LAN access device 220A and the second LANaccess device 220B is identifiable via a second unique Public IP addressassigned to the second LAN access device 220B.

The LAN nodes 238 and 239 may associate with the LAN access devices 220Aand 220B, respectively according to their respective selection criteria.For example, LAN nodes 238 and 239 might associate with the LAN accessdevice with the highest received power as indicated for example by RSSI(Received Signal Strength Indication). Alternatively, nodes mightassociate with LAN access devices based on the bandwidth that the LANaccess devices can service the respective LAN node with, after servicingexisting nodes. The WAN backhaul capacity of a LAN access device mightalso be taken into account to make this choice or selection. Anotherselection criterion might be that a LAN node associates with the LANaccess device servicing fewer existing nodes. In other cases, thesecurity requirements to associate with a LAN access device might leavethe node with only one LAN access device to associate with.

For example, each of the unique Public IP addresses may be assigned byan ISP or service provider which provides internet connectivity to therespective LAN access devices 220A-B. Thus, in accordance with oneembodiment, each of the first and second unique Public IP address aredirectly addressable via a public Internet. In one embodiment, theprivate Internet Protocol (IP) addresses managed by the LAN accessdevice 220A-B are not directly addressable via the Internet, butinstead, must rely upon Network Address Translation (NAT) or someforwarding mechanism, for example, a forwarding mechanism provided by amodem, a router, etc. Thus, in accordance with one embodiment, none ofthe first or second plurality of interconnected LAN nodes 238 and 239are directly addressable via the public Internet as each of the first orsecond plurality of interconnected LAN nodes 238 and 239 require addresstranslation to a corresponding private IP address associated with therespective one of the first or second plurality of interconnected LANnodes 238 and 239 to receive traffic from the public Internet. Forexample, the LAN access devices may be Internet facing, whereas theinterconnected LAN nodes 238 and 239 are not, and are thus protected tosome extent as traffic must first traverse at least the LAN accessdevice before any of the plurality of interconnected LAN nodes 238 and239 can be accessed.

In an alternative embodiment, the first LAN 210A includes a firstplurality of interconnected LAN nodes 238, each of which areidentifiable within the first LAN 210A by one or more Virtual Local AreaNetwork (VLAN) tags managed by the first LAN access device 220A and thesecond LAN 210B includes a second plurality of interconnected LAN nodes239, each of which are identifiable within the second LAN 210B by asecond one or more VLAN tags which are managed by the second LAN accessdevice 220B. In such an alternative embodiment, the first LAN accessdevice 220A provides Voice over Internet Protocol (VoIP) services and/orInternet Protocol Television (IPTV) services to one or more of theinterconnected LAN nodes 238 within the first LAN 220A based on Ethernetlevel addressing using the one or more VLAN tags and the second LANaccess device 220B provides VoIP services and/or IPTV services to one ormore of the interconnected LAN nodes 239 within the second LAN 210Bbased on Ethernet level addressing using the second one or more VLANtags. In this embodiment, any of the first and second plurality ofinterconnected LAN nodes 238 and 239 may be uniquely identifiable basedat least on the one or more VLAN tags respectively managed by the firstor second LAN access device 220A-B. For example, the units may beaddressable over the Internet via remote devices using the one or moreVLAN tags.

In accordance with one embodiment, the traffic aggregation unit 225includes or is allocated or assigned a Public Internet Protocol (IP)address distinct from a public IP address associated with the first LANaccess device 220A and distinct from a public IP address associated withthe second LAN access device 220B. Thus, it is distinctly, uniquely, andseparately identifiable and addressable, separately from either of theLAN access devices 220A-B.

In one embodiment, the first WAN backhaul connection 211 includes orcorresponds to a first transfer rate with the first LAN 210A and thesecond WAN backhaul connection 212 includes or corresponds to a secondaverage transfer rate with the second LAN 210B. In such embodiments, thebonded WAN interface 213 includes or corresponds to an aggregatetransfer rate with the first LAN 210A and with the second LAN 210B whichis greater than the first transfer rate and is greater than the secondtransfer rate of the first and second WAN backhaul connections 211 and212 respectively. Thus, a client device within one of the LANs 210A-B,such as one of the LAN nodes 238, may attain greater transfer ratesusing the logically bonded WAN interface 213 than would be possibleusing only one of the underlying first or second WAN backhaulconnections 211 and 212. For example, the first and second transferrates may constitute one of an instantaneous data rate, an average peakdata rate, or a peak transfer rate, and further in which the aggregatetransfer rate results in data throughput capability which is greaterthan either of the first or the second respective transfer ratesindividually.

In accordance with one embodiment, the traffic aggregation unit 225operates physically separate and distinct from each of the first LANaccess device 220A and the second LAN access device 220B. In such anembodiment, the traffic aggregation unit 225 is communicativelyinterfaced between the first LAN access device 220A and the first WANbackhaul connection 211, in which the traffic aggregation unit has adirect communications link to each of the first LAN access device 220Aand the first WAN backhaul connection 211. In such an embodiment, thetraffic aggregation unit 225 is further communicatively interfaced withthe second LAN access device 220B, in which the traffic aggregation unit225 has an indirect communications link to the second WAN backhaulconnection 212 through the second LAN access device 220B which operatesin direct communication with the second WAN backhaul connection 212. Forexample, the direct communications link communicably interfacing thetraffic aggregation unit 225 between the first LAN access device 220Aand the first WAN backhaul connection 211 may constitute acommunications link with no other intermediate nodes, whereas theindirect communication link to the second WAN backhaul connection 212includes at least one intermediate node before the indirect connectionreaches the second WAN backhaul connection 212.

As depicted, LAN access device 230 is an intermediate node. LAN accessdevice 220B may also serve as an intermediate node as the depicted routetraverses the second LAN access device 220B to reach the second WANbackhaul connection 212. Thus, in accordance with an alternativeembodiment, the system or architecture 200 further includes a third LANaccess device 230 which is communicatively interfaced between thetraffic aggregation unit 225 and the second LAN access device 220B. Insuch an embodiment, the third LAN access device 230 has a directcommunications link to each of the traffic aggregation unit 225 and thesecond LAN access device 220B. In this alternative embodiment, thetraffic aggregation unit 225 has an indirect communications link to thesecond LAN access device 220B through the third LAN access device 230,in which the third LAN access device 230 provides an alternate backupcommunications path to the logically bonded WAN interface 213 over thefirst WAN backhaul connection 211 and the second WAN backhaul connection212 responsive to a failure event at one of the first LAN access device220A or the second LAN access device 220B.

FIG. 2B illustrates an alternative exemplary architecture 201 in whichembodiments may operate. FIG. 2B additionally introduces trafficde-aggregator unit 235.

In accordance with one embodiment, such an architecture 201 or systemfurther includes a traffic de-aggregator unit 235 communicativelyinterfaced between the first WAN backhaul connection 211 and the secondWAN backhaul connection 212. In such an embodiment, the trafficaggregation unit 225 (forming the logically bonded WAN interface 213)bonds Internet Protocol (IP) addresses associated with trafficoriginating from both the first LAN 210A and the second LAN 210B. Insuch an embodiment, the traffic aggregation unit 225 further routes thetraffic having the bonded IP addresses through the traffic de-aggregatorunit 235.

In accordance with one embodiment, the traffic de-aggregator unit 235 ismanaged by a Service Provider that provides one or more of dataconnectivity, voice connectivity, video connectivity, and mobile deviceconnectivity to a plurality of subscribers via the first and second WANbackhaul connections 211 and 212. In such an embodiment, the trafficde-aggregator unit 235 operates physically separate and distinct fromeach of the first LAN access device 220A, the second LAN access device220B, the third LAN access device 230, and the traffic aggregation unit225.

FIG. 2C illustrates an alternative exemplary architecture 202 in whichembodiments may operate. FIG. 2C introduces the traffic aggregation unit225 as an integrated sub-component of a LAN access device 220A.

In accordance with one embodiment, the traffic aggregation unit 225operates as an integrated sub-component of the first LAN access device220A, in which the first LAN access device 220A operates physicallyseparate and distinct from the second LAN access device 220B. In such anembodiment, the traffic aggregation unit 225 is communicativelyinterfaced with the first WAN backhaul connection 211 via acommunications interface of the first LAN access device 220A (e.g.,internal circuitry of 220A, etc.). In such an embodiment, the trafficaggregation unit 225 is communicatively interfaced with the second LANaccess device 220B, in which the traffic aggregation unit 225 uses anindirect communications link to the second WAN backhaul connection 212through the second LAN access device 220B which operates in directcommunication with the second WAN backhaul connection 212.

FIG. 2D illustrates an alternative exemplary architecture 203 in whichembodiments may operate. FIG. 2D introduces the traffic aggregation unit225 as an integrated sub-component of a LAN access device 220A incommunication with a traffic de-aggregator unit 235.

In one embodiment, the described architecture 203 or system includes atraffic de-aggregator unit 235 which is communicatively interfacedbetween the first WAN backhaul connection 211 and the second WANbackhaul connection 212, in which the traffic aggregation unit 225 formsa logically bonded WAN interface 213 over the first WAN backhaul 211 andthe second WAN backhaul 212 by bonding Internet Protocol (IP) addressesassociated with traffic originating from the first LAN 210A and thesecond LAN 210B and by further routing the traffic having the bonded IPaddresses through the traffic de-aggregator unit 235. In accordance withone embodiment, the first WAN 205A and the second WAN 205B and thecorresponding first WAN backhaul connection 211 and second WAN backhaulconnection 212 form an aggregation network via the traffic de-aggregator235, the traffic de-aggregator 235 being connected with Internet WAN 299as shown.

FIG. 2E illustrates an alternative exemplary architecture 204 in whichembodiments may operate. FIG. 2E introduces LAN devices 240 having oneor more wireless transceiver 241 (e.g., each with one or more antennas)to establish one or more wireless communication paths 242A and 242B.Wireless coverage areas 243 are further depicted as are wirelesstransceivers 244A and 244B at the LAN access devices 220A-B.

In one embodiment, at least one of a plurality of LAN devices 240operating within the first LAN 210A use a first communication path tothe first WAN backhaul connection 211 through the first LAN accessdevice 220A and in such an embodiment, at least one of a plurality ofLAN devices 240 operating within the first LAN 210A also use a secondcommunication path to the second WAN backhaul connection 212 through thesecond LAN access device 220B. In such an embodiment, at least one LANdevice 240 includes at least one of: a multiplexing wireless transceiver241 capable to simultaneously maintain a first wireless communicationpath 242A to the first LAN access device 220A and a second wirelesscommunication path 242B to the second LAN access device 220B bymultiplexing between the first and second wireless communication paths242A-B respectively; a wireless transceiver 241 capable to establish thefirst wireless communication path 242A to the first LAN access device220A and capable to establish the wireless second communication path242B to the second LAN access device 220B by terminating the firstwireless communication path 242A and switching to the second wirelesscommunication path 242B; and a first wireless transceiver 241 and asecond wireless transceiver 241, the first and second wirelesstransceivers 241 capable to establish the first wireless communicationpath 242A to the first LAN access device 220A and capable to establishthe wireless second communication path 242B to the second LAN accessdevice 220B either concurrently or not concurrently with the firstwireless communication path 242A to the first LAN access device 220A.

In one embodiment, the first LAN access 220A device is within aresidential premises common to the at least one of a plurality of LANdevices 240 operating within the first LAN 210A and the second LANaccess device 220B is within a second residential premises in aneighboring vicinity to the first residential premises. In such anembodiment, a wireless coverage area 243 associated with the second LANaccess device 220B overlaps with the first residential premises and theat least one of a plurality of LAN devices 240 operating within thefirst LAN 210A. In such an embodiment, the at least one of a pluralityof LAN devices 240 operating within the first LAN 210A establishesconnectivity with the second WAN backhaul connection 212 through thesecond LAN access device 220B responsive to a failure event associatedwith the first LAN access device 220A.

In one embodiment, at least one of a plurality of LAN devices 240operating within the first LAN 210A, responsive to a failure eventassociated with the first LAN access device 220A, establishesconnectivity to the second WAN backhaul connection 212 via a wirelessconnection path 242B between an transceiver 241 of the at least one ofthe plurality of LAN devices 240 within the first plurality of LANdevices 240 and an transceiver 244B of the second LAN access device 220Bwhich is external to, and operationally distinct from, the first LANaccess device 220A. In such an embodiment, the failure event correspondsto a hard failure event characterized by a total loss of connectivitybetween the first LAN access device 220A and the corresponding first WANbackhaul connection 211 or a soft failure event characterized bydegraded connectivity, based on a threshold, between the first LANaccess device 220A and the corresponding first WAN backhaul connection211.

In one embodiment, the wireless connection between the transceiver 241of at least one of the plurality of LAN devices 240 within the first LAN210A and the transceiver 244B of the second LAN access device 220Bconstitutes at least one of the plurality of LAN devices 240 connectingwith the second LAN access device 220B using a guest SSID (Service SetIdentification) on the second LAN access device 220B. In a particularembodiment, the guest SSID on the second LAN access device 220B enablesguest devices (e.g., such as one of LAN devices 240 from the distinctLAN 210A) to communicate with the second WAN backhaul connection 212through the second LAN access device 220B. In such an embodiment, theguest SSID on the second LAN access device 220B further restricts theguest devices from communicating with any devices operating within thesecond LAN 210B without first traversing the second WAN backhaulconnection 212. For example, despite such devices within the second LAN210B being immediately networked to the same LAN access device 220B, theguest devices must nevertheless communicate through the WAN 205A-B, forexample, by establishing communication via the Internet, as if the guestdevices were still connected to their originating LAN access device220A. In so doing, security can be maintained for the secondary networkinfrastructure while allowing the guest devices to utilize the secondWAN backhaul 212 resource.

FIG. 2F illustrates an alternative exemplary architecture 206 in whichembodiments may operate. FIG. 2F introduces a traffic aggregation unit225 as an integrated sub-component within one of a plurality of LANdevices 240A.

In accordance with one embodiment, the traffic aggregation unit 225operates as an integrated sub-component within one of a plurality of LANdevices 240A operating within the first LAN 210A. In such an embodiment,the traffic aggregation unit 225 is communicatively interfaced with thefirst WAN backhaul connection 211 via a communications path to the firstLAN access device 220A which in turn is interfaced via a communicationspath to the first WAN backhaul connection 211. In this embodiment, thetraffic aggregation unit 225, integrated as a sub-component within theone of the plurality of LAN devices 240A operating within the first LAN210A, further is communicatively interfaced with the second LAN accessdevice 220B, in which the traffic aggregation unit 225 uses an indirectcommunications link to the second WAN backhaul connection 212 throughthe second LAN access device 220B which operates in direct communicationwith the second WAN backhaul connection 212.

In one embodiment, the traffic aggregation unit 225 communicates withthe first LAN access device 220A through a wireless communication path242A from the one of the plurality of LAN devices 240A to the first LANaccess device 220A and further wherein the traffic aggregation unit 225communicates with the second LAN access device 220B through a secondwireless communication path 242B from the one of the plurality of LANdevices 240A to the second LAN access device 220B.

In one embodiment, the first and second wireless communication paths242A-B from the one of the plurality of LAN devices 240A to the firstand second LAN access devices 220A-B respectively, include at least oneof: wireless connectivity via a multiplexing wireless transceiver 241that simultaneously maintains the first wireless communication path 242Ato the first LAN access device 220A and the second wirelesscommunication path 242B to the second LAN access device 220B bymultiplexing between the first and second wireless communication paths242A-B respectively; wireless connectivity via a wireless transceiver241 capable to establish the first wireless communication path 242A tothe first LAN access device 220A and capable to establish the wirelesssecond communication path 242B to the second LAN access device 220B byterminating the first wireless communication path 242A and switching tothe second wireless communication path 242A; and wireless connectivityvia a first wireless transceiver 241 and a second wireless transceiver241, the first and second wireless transceivers 241 capable to establishthe first wireless communication path 242A to the first LAN accessdevice 220A and capable to establish the wireless second communicationpath 242B to the second LAN access device 220B, either concurrently ornot concurrently, with the first wireless communication path 242A to thefirst LAN access device 220A.

FIG. 2G illustrates an alternative exemplary architecture 207 in whichembodiments may operate. FIG. 2G re-introduces the traffic de-aggregatorunit 235.

In one embodiment, the architecture 207 or system further includes atraffic de-aggregator unit 235 communicatively interfaced between thefirst WAN backhaul connection 211 and the second WAN backhaul connection212, in which the traffic aggregation unit 225 (which is integrated as asub-component of one of the LAN devices 240A) forms a logically bondedWAN interface 213 over the first WAN backhaul connection 211 and thesecond WAN backhaul connection 212 by bonding Internet Protocol (IP)addresses associated with traffic originating from both the first LAN210A and the second LAN 210B and further by routing the traffic havingthe bonded IP addresses through the traffic de-aggregator unit 235. Thetraffic de-aggregator may be managed by a Service Provider that providesone or more of data connectivity, voice connectivity, videoconnectivity, and mobile device connectivity to a plurality ofsubscribers via the first and second WAN backhaul connections. Thetraffic de-aggregator unit 235 may be physically separate and distinctfrom each of the first LAN access device 220A, the second LAN accessdevice 220B, a third LAN access device 230 (if one is present), and thetraffic aggregation unit 225.

In accordance with the various embodiments described herein, each of thefirst WAN backhaul connection 211 and the second WAN backhaul connection212 are selected from the group of WAN backhaul connections whichincludes: a broadband connection; a Digital Subscriber Line (DSL)connection; a cable connection; a femtocell connection; a mobileconnection; a fiber connection; a wireless connection; and an accessBroadband over Power Line (BPL) connection.

In accordance with the various embodiments described herein, each of thefirst and second LANs 210A and 210B include at least a user device. Inaccordance with the disclosed embodiments, each of the first and secondLAN access devices 220A-B communicably link each of the respective userdevices with one of the first WAN backhaul connection 211 or the secondWAN backhaul connection 212. For example, any one of the interconnectedLAN nodes 238 and 239 or the LAN devices 240 from FIG. 2E, 240A and 240Bmay be a user device.

In accordance with the various embodiments described herein, each of thefirst LAN 210A and the second LAN 210B include a plurality ofinterconnected LAN nodes 238 and 239. In such an embodiment, each of theplurality of interconnected LAN nodes 238 and 239 communicate via atleast one of: an Ethernet based network connection; a wireless basednetwork connection; an Institute of Electrical and Electronics Engineers(IEEE) 802.11 standards based network connection; an 802.11a, 802.11b,802.11g, and/or 802.11n wireless compatible network connection; a femtonetwork connection transmitting via a mobile cellular compatibleprotocol including at least one of a third generation (3G) compatibleprotocol, a fourth generation (4G) compatible protocol, and a Long TermEvolution (LTE) compatible protocol; a power line connection; atelephone system connection; a Plain Old Telephone Service (POTS)connection; a G.hn (ITU-T standardized unified high-speed wire-linebased home networking) connection; and a Coax cable connection.

In accordance with the various embodiments described herein, each of thefirst LAN access device 220A and the second LAN access device 220B areselected from the group of access devices which includes: a basestation; an access point; a modem; a router; a gateway; a DigitalSubscriber Line (DSL) Customer Premises Equipment (CPE) modem; anin-home power line device; a Home Phoneline Network Alliance (HPNA)based device; an in-home coax distribution device; a G.hn compatibledevice; an in-home metering communication device; an in-home appliancecommunicatively interfaced with the LAN; a wireless femtocell basestation; a wireless compatible base station; a wireless mobile devicerepeater; a wireless mobile device base station; a set-top box(STB)/set-top unit (STU) customer electronics device; an InternetProtocol (IP) enabled television; an IP enabled media player; an IPenabled gaming console; an Ethernet gateway; a computing deviceconnected to the LAN; a HomePlug device; an IEEE P1901 standardscompatible access Broadband over Power Line (BPL) device; an Ethernetconnected computer peripheral device; an Ethernet connected router; anEthernet connected wireless bridge; an Ethernet connected networkbridge; and an Ethernet connected network switch.

FIG. 2H illustrates an alternative exemplary architecture 208 in whichembodiments may operate. FIG. 2H introduces a traffic aggregation unit225 as an integrated sub-component within one a third LAN access device230.

In one embodiment, the architecture 208 or system further includes athird LAN access device 230 which is communicably interfaced between thefirst LAN access device 220A and the second LAN access device 220B. Insuch an embodiment the traffic aggregation unit 225 operates as anintegrated sub-component of the third LAN access device 230, in whichthe third LAN access device 230 operates physically separate anddistinct from each of the first LAN access device 220A and the secondLAN access device 220B.

In one embodiment, the traffic aggregation unit uses a first connection,via a device communicably interfaced with the second LAN access device220B and uses a second connection to communicably interface the trafficaggregation unit 225 with the first WAN backhaul connection 211. In suchan embodiment, a data aggregation unit 231 combines traffic from thefirst connection and traffic from the second connection into aggregatedtraffic.

In one embodiment, a data de-aggregation unit 236 is communicablyinterfaced with the first WAN backhaul connection 211 and communicablyinterfaced with the second WAN backhaul connection 212. In such anembodiment, the data de-aggregation unit 236 de-aggregates traffic ontothe first connection and onto the second connection as de-aggregatedtraffic.

FIG. 3A illustrates an alternative exemplary architecture 300 in whichembodiments may operate. Depicted are a first Wide Area Network (WAN) atelement 305A and a second WAN at 305B. WAN 305A being connected withLocal Area Network (LAN) 310A via WAN backhaul connection 311 and WAN305B being connected with LAN 310B via WAN backhaul connection 312.

In accordance with one embodiment, such an architecture 300 or systemincludes a first Local Area Network (LAN) access device 320A toestablish a first LAN 310A and a second LAN access device 320B toestablish a second LAN 310B which is operationally distinct from thefirst LAN 310A. In this embodiment, a first Wide Area Network (WAN)backhaul connection 311 provides the first LAN access device 320A withWAN connectivity and a second WAN backhaul connection 312 provides thesecond LAN access device 320B with WAN connectivity, in which each ofthe first WAN backhaul connection 311 and the second WAN backhaulconnection 312 are physically distinct. This embodiment further includesa management device 325 communicatively interfaced with each of thefirst LAN access device 310A, the second LAN access device 310B, thefirst WAN backhaul connection 311, and the second WAN backhaulconnection 312. In such an embodiment, the management device 325,responsive to a failure event, re-routes traffic associated with thefirst LAN 310A onto the second WAN backhaul connection 312 or re-routestraffic associated with the second LAN 310B onto the first WAN backhaulconnection 311.

FIG. 3B illustrates an alternative exemplary architecture 301 in whichembodiments may operate. In accordance with one embodiment, themanagement device 325 is implemented within the first LAN access device320A and communicatively interfaced with the LAN access device 320A viaan internal communications bus of the first LAN access device (e.g., viainternal circuitry). In such an embodiment, the management device 325 iscommunicatively interfaced with each of the second LAN access device320B, the first WAN backhaul connection 311, and the second WAN backhaulconnection 312 via one or more communication paths 350 external to thefirst LAN access device 320A.

FIG. 3C illustrates an alternative exemplary architecture 302 in whichembodiments may operate. In accordance with one embodiment, themanagement device 325 is implemented within a WAN access device 335Acommunicatively coupled with the first WAN backhaul connection 311 viaan internal communications bus of the first WAN access device (e.g., viainternal circuitry). In such an embodiment, the management device 325 iscommunicatively interfaced with each of the first LAN access device320A, the second LAN access device 320B, and the second WAN backhaulconnection 312 via one or more communication paths 350 external to thefirst WAN access device 335A.

FIG. 3D illustrates an alternative exemplary architecture 303 in whichembodiments may operate. In accordance with one embodiment, themanagement device 325 is implemented as an externally separate andphysically distinct device from a first WAN access device 335Acommunicatively coupled with the first WAN backhaul connection 311, asan externally separate and physically distinct device from a second WANaccess device 335B communicatively coupled with the second WAN backhaulconnection 312, as an externally separate and physically distinct devicefrom the first LAN access device 320A, and as an externally separate andphysically distinct device from the second LAN access device 320B. Insuch an embodiment, the management device 325 is communicativelyinterfaced with each of the first WAN access device 335A, the second WANaccess device 335B, the first LAN access device 320A, and the second LANaccess device 320B, via one or more communication paths 350 external tothe externally separate and physically distinct implementation of themanagement device 325.

FIG. 3E illustrates an alternative exemplary architecture 304 in whichembodiments may operate. In accordance with one embodiment, such anarchitecture 304 or system further includes a traffic aggregation unit345 which operates externally separate and physically distinct from eachof the first LAN access device 320A and the second LAN access device320B. In such an embodiment, the traffic aggregation unit 345 forms alogically bonded WAN interface 313 over the first WAN backhaul 311 andthe second WAN backhaul 312. In accordance with this embodiment, themanagement device 325 is implemented within the traffic aggregation unit345 and is communicatively interfaced with each of the first LAN accessdevice 320A, the second LAN access device 320B, the first WAN backhaulconnection 311, and the second WAN backhaul connection 312 via one ormore communication paths 350 external to the traffic aggregation unit345.

In accordance with several of the various embodiments, the trafficaggregation unit 345 or the management device 325 operates in accordancewith Synchronous optical networking (SONET) or synchronous digitalhierarchy (SDH) multiplexing protocols. In one embodiment, the trafficaggregation unit 345 or the management device 325, responsive to afailure event, re-routes the traffic by performing a SONET or SDHcompatible rapid re-route function. In one the traffic aggregation unit345 or the management device 325, responsive to a failure event,re-routes the traffic via an Ethernet Resilient Packet Ring (RPR)implementation.

In accordance with one embodiment, the management device 345, responsiveto a failure event, re-routes the traffic by instituting one or more ofthe following events: (a) performing a first traffic re-route operationresponsive to a hard failure event characterized by a total loss ofconnectivity for one of the first LAN access device 320A and the secondLAN access device 320B with the corresponding first or second WANbackhaul connection 311 or 312; or (b) performing a second trafficre-route operation responsive to a soft failure event characterized bydegraded connectivity as determined by a threshold for one of the firstLAN access device 320A and the second LAN access device 320B with thecorresponding first or second WAN backhaul connection 311 or 312. Insuch an embodiment, the first traffic re-route operation may bedifferent than the second traffic re-route operation.

FIG. 4A illustrates an alternative exemplary architecture 400 in whichembodiments may operate. Depicted are a first Wide Area Network (WAN) atelement 405A and a second WAN at 405B. WAN 405A being connected withLocal Area Network (LAN) 410A via WAN backhaul connection 411 and WAN405B being connected with LAN 410B via WAN backhaul connection 412.

In accordance with one embodiment, such an architecture 400 or systemincludes a first Local Area Network (LAN) access device 420A toestablish a first LAN 410A and a second LAN access device 420B toestablish a second LAN 410B operationally distinct from the first LAN410A. In such an embodiment, a first Wide Area Network (WAN) backhaulconnection 411 provides the first LAN access device 420A with WANconnectivity and a second WAN backhaul connection 412 provides thesecond LAN access device 420B with WAN connectivity, in which each ofthe first WAN backhaul connection 411 and the second WAN backhaulconnection 412 are physically distinct. In this embodiment, a managementdevice 425 is communicatively interfaced with each of the first LANaccess device 420A, the second LAN access device 420B, the first WANbackhaul connection 411, and the second WAN backhaul connection 412. Inthis embodiment, the management device 425 routes a first portion 498 oftraffic originating from the first LAN 410A over the first WAN backhaulconnection 411 and the management device 425 further routes a secondportion 499 of the traffic originating from the first LAN 410A over thesecond WAN backhaul connection 412.

In one embodiment, the management device 425 routes the first portion498 of traffic over the first WAN backhaul connection 411 and furtherroutes the second portion 499 of the traffic over the second WANbackhaul connection 412 to implement load-balancing for the first LAN410A.

In one embodiment, the management device 425 implements load balancingfor the second LAN 410B by routing a first portion 444 of trafficoriginating from the second LAN 410B over the second WAN backhaulconnection 412 and by further routing a second portion 445 of thetraffic originating from the second LAN 410B over the first WAN backhaulconnection 411. Management device 425 may implement load balancing forthe respective first and/or second LANs regardless of whether themanagement device is internal to LAN access device 420A or 420B.

In one embodiment, the management device 425 implementing load balancingincludes determining what portions of traffic 498 and 499 to route overthe first and second WAN backhauls, respectively, based on factors suchas bandwidth capacity of the first and second WAN backhauls, or based onother factors such as payment options chosen by the first and secondsubscribers, or conditions imposed by their internet service providers,based on a number of nodes associated with each of the LAN accessdevices, based on traffic patterns of each of the nodes, the securityoptions, or the capacity and capabilities of the LAN access devices etc.These factors, among others, will cause the management device 425 tovary the portion of traffic to route across the first and second WANbackhauls.

In one embodiment, traffic portion 498 includes control and managementtraffic and traffic portion 499 includes the payload portion of trafficcorresponding to traffic portion 498. In such an embodiment, themanagement device 425 implements load balancing for the first LAN 410Aby routing the first portion 498 of traffic over the first WAN backhaulconnection 411 and further routes the second portion 499 of the trafficover the second WAN backhaul connection 412. Separating or splitting thepayload and control traffic portions in such a way reduces the overheadcaused due to the control and management traffic. For example, when anIEEE 802.11n LAN access device is operating in the presence of a legacystation operating on IEEE 802.11b, there will be substantial overheaddue to control frames such as RTS/CTS and ACK. In such an event, routingall the control traffic over the second WAN backhaul can help reduceoverhead and improve throughput.

FIG. 4B illustrates an alternative exemplary architecture 401 in whichembodiments may operate. In accordance with one embodiment, first LANaccess device is a wireless LAN access device 421 having a firsttransfer rate for the first LAN 410A which is greater than a secondtransfer rate for the first WAN backhaul connection 411, in which thesecond transfer rate for the first WAN backhaul connection 411 results(e.g., causes) a bottleneck to the traffic (e.g., the first and secondportions 498 and 499) originating from the wireless LAN access device421 directed to the first WAN backhaul connection 411. In oneembodiment, the management device 425 implements load-balancing for thefirst LAN 410A by routing the first portion 498 of traffic over thefirst WAN backhaul connection 411 at a rate which is less than thesecond transfer rate for the first WAN backhaul connection 411 andfurther by routing the second portion of the traffic 499 over the secondWAN backhaul connection 412, in which the second portion 499 of thetraffic is a remaining portion of the traffic originating from the firstLAN 410A.

In one embodiment, the management device 425 implements load-balancingfor the first LAN 410A by implementing an aggregate transfer rate forWAN connectivity provided to the first LAN 410A by the wireless LANaccess device 421 and by implementing an aggregate transfer rate for WANconnectivity provided to the second LAN 410B, in which the aggregatetransfer rate for WAN connectivity is greater than the second transferrate for the first WAN backhaul connection 411. For example, byutilizing both the first and second WAN backhaul connections 411 and412, an aggregate transfer rate for WAN connectivity can be realized forthe LANs 410A-B which is greater than they would otherwise attain fromusing only their respective single WAN backhaul connections (e.g.,either 411 or 412, but not both). In an alternative embodiment, themanagement device 425 implements load-balancing for the first LAN 410Aby assigning incoming flows to the most lightly-loaded WAN connection.For example, the management device 425 may assign, route, or otherwiseplace a new incoming flow, such as a new VoIP connection or Internet TVstream, onto the most lightly-loaded WAN connection.

In one embodiment, the management device 425 routes the first portion498 of traffic over the first WAN backhaul connection 411 and furtherroutes the second portion 499 of the traffic over the second WANbackhaul connection 412 by allocating a portion of bandwidth associatedwith the second WAN backhaul connection 412 to the first LAN accessdevice (e.g., 420A from FIG. 4A or the wireless LAN access device 421 ofFIG. 4B), in which the allocation is based on a paid subscription tieror a service level tier associated with the first LAN access device(420A or 421). For example, the paid subscription tier or a servicelevel tier may be chosen by a user when signing up for service from aservice provider. A user may elect to pay an increased subscription feeto enable a higher aggregate transfer rate than is otherwise attainablefrom using only a single WAN backhaul connection 411 or 412.Alternatively, a user might obtain a subsidized subscription fee toallow other users access to his unused WAN bandwidth.

FIG. 4C illustrates an alternative exemplary architecture 402 in whichembodiments may operate. In accordance with one embodiment, thearchitecture 402 or system further includes a wireless communicationslink 422 between the first LAN access device operating as a wireless LANaccess device 421 and the second LAN access device operating as a secondwireless LAN access device 423. In such an embodiment, the managementdevice 425 instructs the wireless LAN access device 421 to route orswitch the second portion of traffic 499 over the wirelesscommunications link 422 from the first wireless LAN access device 421 tothe second wireless LAN access device 423 and onto the second WANbackhaul connection 412.

In one embodiment, the second LAN access device 423 can operate as awireless LAN access device, distinct from the first wireless LAN accessdevice 421. The communication link 422 may be a wireless communicationlink between the first LAN access device operating as a wireless LANaccess device 421 and the second LAN access device operating as a secondwireless LAN access device 423.

In accordance with one embodiment, the first WAN backhaul connection 411provides the first LAN access device (e.g., 420A at FIG. 4A or 421 atFIG. 4C) with WAN connectivity via the first WAN backhaul connection 411to a Service Provider that provides one or more of data connectivity,voice connectivity, video connectivity, and mobile device connectivityto a plurality of subscribers. In this embodiment, the second WANbackhaul connection 412 provides the second LAN access device (e.g.,420B at FIG. 4A or 423 at FIG. 4C) with WAN connectivity via the secondWAN backhaul connection 412 to the same Service Provider via aphysically distinct communications link to the same Service Provider.

In one embodiment, the first WAN backhaul connection 411 provides thefirst LAN access device (420A or 421) with WAN connectivity via thefirst WAN backhaul connection 411 to a first Service Provider thatprovides one or more of data connectivity, voice connectivity, videoconnectivity, and mobile device connectivity to a plurality ofsubscribers and in this embodiment, the second WAN backhaul connection412 provides the second LAN access device (420B or 423) with WANconnectivity via the second WAN backhaul connection 412 to a secondService Provider which is separate and distinct from the first ServiceProvider.

FIG. 4D illustrates an alternative exemplary architecture 403 in whichembodiments may operate. In accordance with one embodiment, thearchitecture 403 or system further includes the management device 425collecting a first information set 470A about the first WAN backhaulconnection 411; further includes the management device 425 collecting asecond information set 470B about the first LAN 410A; further includesthe management device 425 collecting a third information 470C set aboutthe second WAN backhaul connection 412; and further includes themanagement device 425 collecting a fourth information set 470D about thesecond LAN 410B. In such an embodiment, the management device 425jointly analyzes at least a portion from each of the first, second,third, and fourth information sets 470A-D collected and identifies anoperational condition 471 affecting the first and second WAN backhaulconnections 411-412 and further affecting the first and second LANs410A-B based on the jointly analyzed collected information sets 470A-D.In accordance with such an embodiment, the management device 425initiates a management event 472 responsive to the operational condition471 being identified.

In one embodiment, responsive to the operational condition 471 beingidentified, the management device 425 initiating the management event472 constitutes generating instructions specifying a configurationchange to one or more of: a configuration change for a channelallocation associated with a wireless based first LAN access device 420Aor a wireless based second LAN access device 420B, or both; aconfiguration change to a power allocation scheme for signals associatedwith the wireless based first LAN access device 420A or the wirelessbased second LAN access device 420B, or both; a configuration change toSTA (Station) to AP (Access Point) associations associated with thewireless based first LAN access device 420A or the wireless based secondLAN access device 420B, or both; a configuration change to beacon powercharacteristics associated with the wireless based first LAN accessdevice 420A or the wireless based second LAN access device 420B, orboth; a configuration change to beacon intervals associated with thewireless based first LAN access device 420A or the wireless based secondLAN access device 420B, or both; a configuration change to transmissionrates associated with the wireless based first LAN access device 420A orthe wireless based second LAN access device 420B, or both; aconfiguration change to beamforming characteristics of the wirelessbased first LAN access device 420A or the wireless based second LANaccess device 420B, or both; a configuration change to a Request toSend/Clear to Send (RTS/CTS) configuration associated with the wirelessbased first LAN access device 420A or the wireless based second LANaccess device 420B, or both; a configuration change to fragmentationconfiguration of the wireless based first LAN access device 420A or thewireless based second LAN access device 420B, or both; a configurationchange to the wireless mode (e.g. IEEE 802.11a/b/g/n) configuration ofthe wireless based first LAN access device 420A or the wireless basedsecond LAN access device 420B, or both; a configuration change to thebandwidth utilized by the wireless based first LAN access device 420A orthe wireless based second LAN access device 420B, or both (example,channel bonding in IEEE 802.11n); a configuration change to frameaggregation of traffic from the wireless based first LAN access device420A or the wireless based second LAN access device 420B, or both; aconfiguration change to guard interval of the wireless based first LANaccess device 420A or the wireless based second LAN access device 420B,or both; a configuration change to an antenna array configuration of thewireless based first LAN access device 420A or to the wireless basedsecond LAN access device 420B, or both; a configuration change topreamble length used by the wireless based first LAN access device 420Aor the wireless based second LAN access device 420B, or both; aconfiguration change to handoff techniques of the wireless based firstLAN access device 420A or the wireless based second LAN access device420B, or both; a configuration change to power saving modes of thewireless based first LAN access device 420A or the wireless based secondLAN access device 420B, or both; and a configuration change to maximumnumber of retransmission attempts of the wireless based first LAN accessdevice 420A or the wireless based second LAN access device 420B, orboth.

The wireless based LAN access devices involved in this configuration maybe chosen from a wider set of wireless based LAN access devices alreadyavailable. Such LAN access devices may support high throughput. In oneembodiment, selection of these LAN access devices is based on one ormore of a Received Signal Strength Indicator (RSSI), a wireless bitrate, channel usage, pre-existing traffic loads, overall achievablethroughput, other similar performance indicators, or by using acombination of such indicators to estimate available throughput.

In one embodiment, the management event 472 is selected from the groupof management events 472 which includes sending instructions 478 toestablish a direct communications link 476 between the first LAN accessdevice 420A and the second LAN access device 420B responsive to thejoint analysis indicating an operational problem (e.g., such as theidentified operational condition 471) with the first WAN backhaulconnection 411. For example, the operational problem may be derived fromor correspond to the identified operational condition 471.

FIG. 4E illustrates an alternative exemplary architecture 404 in whichembodiments may operate. In accordance with one embodiment, themanagement event 472 is selected from the group of management events 472which includes sending instructions 478 to establish a directcommunications link 476 between a node 477 operating within the firstLAN 410A, and the second LAN access device 420B, responsive to the jointanalysis indicating an operational problem with the first LAN accessdevice 410A. For example, responsive to the operational condition 471being identified. The instructions 478 may correspond to or be derivedfrom the management event 472. In accordance with the disclosedembodiments, node 477 may be implemented as one of a wireless node, amobile node, or as a LAN device node.

In accordance with several of the various embodiments, the managementdevice 425 jointly analyzes the collected information sets 470A-D byanalyzing bandwidth usage over time of the first LAN 410A and bandwidthusage over time of the second LAN 410B and detects, as the operationalcondition 471, a traffic imbalance between the first LAN 410A and thesecond LAN 410B. In such an embodiment, initiating the management event472 constitutes the management device 425 allocating unused bandwidthassociated with the first WAN backhaul connection 411 to the second LANaccess device 420A or constitutes allocating unused bandwidth associatedwith the second WAN backhaul connection 412 to the first LAN accessdevice 420A based on the identified traffic imbalance between the firstLAN 410A and the second LAN 410B.

In one embodiment, initiating the management event 472 constitutes themanagement device 425 determining whether a LAN access device has unusedbandwidth at a given time of the day or week. In such an embodiment, inaddition to or as an alternative to utilizing the bandwidth for a secondLAN device, multiple SSIDs may be used to open the unused bandwidth forpublic or private usage during the given time of the day or week orduring some other specified time.

In accordance with several of the various embodiments, the secondinformation set 470B about the first LAN 410A and the fourth informationset 470D about the second LAN 410B each include information specific toa first communication layer of the first and second LANs 410A-B and thefirst information set 470A about the first WAN backhaul connection 411and the third information set 470C about the second WAN backhaulconnection 412 includes information specific to a second communicationlayer of the first and second WAN backhaul connections 411-412 which isdifferent than the first communication layer of the first and secondLANs 410A-B.

FIG. 4F illustrates an alternative exemplary architecture 406 in whichembodiments may operate. In accordance with one embodiment, the secondinformation set 470B about the first LAN 410A and the fourth informationset 470D about the second LAN 410B each include neighborhood analysisrelating to Internet connectivity provided to a plurality of otherlocations in a shared geographical area 469 with the management device425. In such an embodiment, the management device 425 initiating themanagement event 472 responsive to the operational condition 471 beingidentified constitutes generating instructions 479 to change aconfiguration of the first WAN backhaul connection 411 or constitutesgenerating instructions 479 to change a configuration of the second WANbackhaul connection 412, or both, based on the neighborhood analysis.

In accordance with one embodiment, the first information set 470A aboutthe first WAN 410A and the third information set 470C about the secondWAN 410B each include neighborhood analysis relating to Internetconnectivity provided to a plurality of other locations in a sharedgeographical area 469 with the management device and the managementdevice 425 initiating the management event 472 responsive to theoperational condition being identified 471 constitutes the managementdevice 425 generating instructions 479 to change a configuration of thefirst LAN access device 420A or the second LAN access device 420B, orboth, based on the neighborhood analysis. The neighborhood analysis andthe various information sets 470A-D depicted at FIGS. 4D through 4F maybe utilized in association with the other disclosed embodimentsdescribed herein, including all of the exemplary embodiments depictedand described with regard to FIGS. 4A through 4E.

In one embodiment, the management device 425 initiating the managementevent 472 responsive to the operational condition being identified 471constitutes the management device 425 generating instructions 479 tomodify the identified operational condition 471 in which the managementdevice 425 communicates the generated instructions 479 to one or moreof: a network element 466, a WAN device 468, and/or a LAN device 467communicatively interfaced with the management device and further inwhich the generated instructions 479 are communicated via a protocolselected from the group of protocols which includes: a TR-069 (TechnicalReport 069) compatible communications protocol; a Transmission ControlProtocol/Internet Protocol (TCP/IP) communications protocol; a SimpleNetwork Management Protocol (SNMP) communications protocol; anout-of-band telephone line protocol; a Digital Subscriber Line EmbeddedOperations Channel (DSL EOC) communications protocol; a cable controlchannel communications protocol; a power line control channelcommunications protocol; a Command Line Interface (CLI) protocol; and aTransaction Language 1 (TL1) communications protocol.

In accordance with one embodiment, the first WAN backhaul connection 411and the second WAN backhaul connection 412 are each communicablyinterfaced with the management device 425 via one of: a wireless networkconnection; a wired network connection; a Digital Subscriber Line (DSL)network connection; a power line network connection; a Passive OpticalNetwork (PON) based network connection; a fiber optic based networkconnection; and a cable based network connection.

In one embodiment, the management device 425 is one of: a DigitalSubscriber Line (DSL) modem operating as a Customer Premises Equipment(CPE) device to communicatively interface a DSL based backhaul providedvia the first WAN backhaul connection 411 to the first LAN 410A; a cablemodem operating to communicatively interface a cable network basedbackhaul provided via the first WAN backhaul connection 411 to the firstLAN 410A; a wireless modem operating to communicatively interface awireless based backhaul provided via the first WAN backhaul connection411 to the first LAN 410A; a power line modem operating tocommunicatively interface a power line based backhaul provided via thefirst WAN backhaul connection 411 to the first LAN 410A; an OpticalNetwork Terminal (ONT) operating to communicatively interface a fiberoptic based backhaul provided via the first WAN backhaul connection 411to the first LAN 410A; a router operating to communicatively interfacethe first WAN backhaul connection 411 to the first LAN 410A; a gatewayoperating to communicatively interface the first WAN backhaul connection411 to the first LAN 410A; and a computing device remotely located froma WAN/LAN interface through which a communication channel related to thefirst WAN backhaul connection 411 and the first LAN 410A is connected,in which the computing device provides remote monitoring and managementfunctionality for the WAN/LAN interface.

In accordance with the various embodiments, the management device 425collecting the first, second, third, and fourth information sets 470A-Dconstitutes the management device 425 collecting each of the informationsets 470A-D from an information source selected from the group ofinformation sources which includes: a Digital Subscriber Line (DSL)Customer Premises Equipment (CPE) modem; an in-home power line device; aHome Phoneline Network Alliance (HPNA) based device; an in-home coaxdistribution device; a G.hn compatible device; an in-home meteringcommunication device; an in-home appliance communicatively interfacedwith the LAN; a wireless femtocell base station; a wireless compatiblebase station; a wireless mobile device repeater; a wireless mobiledevice base station; a set-top box (STB)/set-top unit (STU) customerelectronics device; an Internet Protocol (IP) enabled television; an IPenabled media player; an IP enabled gaming console; an Ethernet gateway;a computing device connected to the LAN; an Ethernet connected computerperipheral device; an Ethernet connected router; an Ethernet connectedwireless bridge; an Ethernet connected network bridge; and an Ethernetconnected network switch.

In accordance with the various embodiments, the first WAN backhaulconnection 411 and the second WAN backhaul connection 412 are selectedfrom the group of WAN backhaul connections 411 and 412 which include: abroadband connection; a DSL connection; a cable connection; a femtocellconnection; a mobile connection; a fiber connection; a wirelessconnection; and an access Broadband over Power Line (BPL) connection.

In one embodiment, each of the first LAN 410A and the second LAN 410Binclude a plurality of interconnected LAN nodes 238. In such anembodiment, each of the plurality of interconnected LAN nodes 238communicate via at least one of: an Ethernet based network connection; awireless based network connection; an Institute of Electrical andElectronics Engineers (IEEE) 802.11 standards based network connection;an 802.11a, 802.11b, 802.11g, 802.11ad at 60 GHz, and/or 802.11nwireless compatible network connection; a femto network connectiontransmitting via a mobile cellular compatible protocol including atleast one of a third generation (3G) compatible protocol, a fourthgeneration (4G) compatible protocol, and a Long Term Evolution (LTE)compatible protocol; a power line connection; a telephone systemconnection; a Plain Old Telephone Service (POTS) connection; a G.hn(ITU-T standardized unified high-speed wire-line based home networking)connection; and a Coax cable connection.

In one embodiment, each of the first LAN access device 420A and thesecond LAN access device 420B are selected from the group of deviceswhich includes: a base station; an access point; a modem; a router; agateway; a Digital Subscriber Line (DSL) Customer Premises Equipment(CPE) modem; an in-home power line device; a Home Phoneline NetworkAlliance (HPNA) based device; an in-home coax distribution device; aG.hn compatible device; an in-home metering communication device; anin-home appliance communicatively interfaced with the LAN; a wirelessfemtocell base station; a wireless compatible base station; a wirelessmobile device repeater; a wireless mobile device base station; a set-topbox (STB)/set-top unit (STU) customer electronics device; an InternetProtocol (IP) enabled television; an IP enabled media player; an IPenabled gaming console; a 60 GHz capable station; PAN (Personal AreaNetworks) capable device; an Ethernet gateway; a computing deviceconnected to the LAN; an Ethernet connected computer peripheral device;an Ethernet connected router; an Ethernet connected wireless bridge; anEthernet connected network bridge; and an Ethernet connected networkswitch.

In one embodiment, each of the first LAN 410A and the second LAN 410Binclude a plurality of interconnected LAN nodes 238 and each of theplurality of interconnected LAN nodes 238 are selected from the group ofnodes which includes: a computer with LAN connectivity; a notebook withLAN connectivity; a mobile phone with LAN connectivity; a game consolewith LAN connectivity; an electronic computing machine with LANconnectivity; an IPTV with LAN connectivity; storage devices with LANconnectivity; devices that are primarily purposed for other applicationsand can have LAN connectivity, for example, household lighting, alarmsystems, heating/cooling and other household appliances, etc.

FIG. 4G illustrates an alternative exemplary architecture 407 in whichembodiments may operate. In accordance with certain embodiments, themanagement device 425 collects, for joint analysis, information from theLANs 410A, 410B, 410C, 410D, 410E, and 410F, including neighborhoodanalysis 440 relating to Internet connectivity provided to a pluralityof locations in a neighborhood or a shared geographical area 469 withthe management device 425. In such an embodiment, initiating amanagement event 472 includes a management device 425 generatinginstructions or commands to change a configuration of a WAN device basedon the neighborhood analysis 440 collected. In an alternativeembodiment, initiating a management event 472 includes a managementdevice 425 generating instructions to change a configuration of a LANdevice (e.g., one of nodes 477A-C) based on the neighborhood analysis440.

Joint analysis by the management device 425 may include conductingneighborhood analysis including aggregating information multiple sourcesto provide a broader analytical context. For example, nodes 477A, 477B,and 477C are depicted as traversing a shared back-haul 414 to a WAN405A. WAN 405A includes a management device 425 implemented as describedherein. Because nodes 477A-C all traverse a common or shared back-haul414, information may be retrievable from each of the nodes 477A-C andcorrespondingly from Local Area Networks 410A, 410B, and 410Crespectively. The information may be collected by management device 425within WAN 405A and utilized to optimize the WAN and LAN networks andthe communication paths between the respective WAN and LAN networks.

For example, a shared back-haul 414 may exist with DSL networks in whichmultiple twisted pair lines traverse a common DSL binder; a sharedback-haul 414 may be present with multiple coaxial cable internetcustomers each contending for WAN based resources over a single coaxialcable over which at least a portion of WAN back-haul is implemented; ashared back-haul 414 may be present with a power line based Internetservice provider in which multiple LANs (e.g., 410A-C) associated withdistinct end-users contend for WAN based resources over the samephysical transmission lines; a shared back-haul 414 may similarly bepresent where multiple LANs (e.g., 410A-C) associated with distinctend-users contend for WAN based resources over the same wirelesstransmission spectrum; a shared back-haul 414 may be present with fiberoptic based connections each contending for WAN based resources; or ashared back-haul 414 may comprise of a combination of the abovecommunication means, such as a combination of coaxial cable, fiber andtwisted pairs.

In such embodiments, a management device 425 may collect informationfrom multiple distinct LANs and analyze the collected information fromthe multiple LANs to identify an operational condition 471. Suchanalysis may be referred to as neighborhood analysis. The managementdevice 425 may then report, diagnose, monitor, or generate instructionsto implement an operational change via a management event 472 based onthe neighborhood analysis. For example, the management device 425 mayimplement WAN/LAN network optimizations which include increasingtransmit power and data rates to one LAN (e.g., 410A) based ondetermination that another LAN represented within the neighborhoodanalysis is inactive or has a low activity rate (e.g., LAN 410C may bedetermined to be underutilized). In such an embodiment, a correspondingdecrease of transmit power and data rate may be implemented for theunderutilized LAN (e.g., 410C in such an example).

In another embodiment, neighborhood analysis may indicate that theshared back-haul 414 is saturated due to a demand load in excess ofcapacity based on analysis of LAN information retrieved from themultiple distinct LANs 410A-C in which case the management device 425may responsively implement a load-balancing algorithm on a WAN/LANinterface (e.g., a DSL modem, cable modem, ONT unit, etc.) interfacingeach of the respective LANs 410A-C to the single shared back-haul 414.In such a way, overall network efficiency may be improved by reducingcollisions, buffering queues, data re-transmits, and other excessiveoverhead waste that may occur due to an overwhelmed networkcommunication path, such as a shared WAN back-haul 414.

In accordance with an alternative embodiment, a collection module of amanagement device 425 collects the neighborhood analysis from a WANoperator (e.g., WAN 405B), where the neighborhood analysis describes LANwireless transmission channels for a plurality of locations in a sharedgeographical area 469 with the management device. For example, withinthe neighborhood or shared geographical area 469 are multiple distinctLANs 410D, 410E, and 410F. Each of the distinct LANs 410D-F aretransmitting information 440 to WAN 405B, such as an ISP or Wide AreaNetwork Operator. The information 440 sent via each of the LANs maydescribe various characteristics about the LAN from which theinformation originated. In one embodiment, the WAN 405B aggregates theinformation 440 and makes the aggregate information available asneighborhood analysis. Each management device 425 within each of therespective LANs 410D-F may then collect and analyze the neighborhoodanalysis, and may additionally implement operational changes within acorresponding LAN 410D-F based on the information collected from the WAN405B.

Thus, in accordance with one embodiment, instructions are generated by amanagement device 425 to change the configuration of a LAN device basedon the neighborhood analysis. In one embodiment, the generatedinstructions select a LAN wireless transmission channel for a LAN devicecommunicatively interfaced with the management device 425 that minimizeswireless interference between the LAN device and a plurality of otherlocations in the neighborhood or shared geographical area 469 with themanagement device 425. In some embodiments, each of the managementdevices within the various LANs 410D-F implement similar instructions,although, the management devices 425 within the respective LANs 410D-Fneed not have operational awareness of any other management device 425as the neighborhood analysis is collected from WAN 405B. In alternativeembodiments, a management device within the WAN 405B or locatedelsewhere may initiate instructions to implement an operational changevia a management event 472 within the WAN 405B or within multipledistinct LANs 410D-F.

In the above embodiment, operational efficiency of the individual LANs410A-F may be improved by reducing interference between closely locatedLANs, based on the neighborhood analysis. Such information may becorrelated by a WAN operator based on, for example, mapping overlappingidentifiers to a virtually rendered neighborhood or shared geographicarea 469 or alternatively, based on actual knowledge of geographiclocations for multiple LANs 410, for example, by cross referencingsubscribers' service address information to physical locations.

Diagnostics may similarly rely upon neighborhood analysis yielded frommultiple distinct LANs 410. For example, multiple LAN devices 410A-Fexhibiting high error counts, or abnormal retrains/modem resets, may beindicative of a fault within the WAN 405A-B infrastructure rather than astatistically less likely coincidence that multiple LAN side devices areeach simultaneously exercising a similar fault. In a complementary way,neighborhood analysis from multiple LANs 410A-F within a commongeographical area or multiple LANs associated with a single sharedback-haul 414 may aid in systematically diagnosing a LAN side faultwithin a particular end-user consumer's local area network where similardevices operating in neighboring LANs 410A-F do not presentcorresponding errors or faults within the neighborhood analysis.

FIG. 5A shows a diagrammatic representation of a system 500 inaccordance with which embodiments may operate, be installed, integrated,or configured.

In one embodiment, system 500 includes a memory 595 and a processor orprocessors 596. For example, memory 595 may store instructions to beexecuted and processor(s) 596 may execute such instructions.Processor(s) 596 may also implement or execute implementing logic 560having logic to implement the methodologies discussed herein. System 500includes communication bus(es) 515 to transfer transactions,instructions, requests, and data within system 500 among a plurality ofperipheral devices communicably interfaced with one or morecommunication buses 515. In one embodiment, system 500 includes acommunication bus 515 to interface, transfer, transact, relay, andand/or communicate information, transactions, instructions, requests,and data within system 500, and among plurality of peripheral devices.System 500 further includes management interface 525, for example, toreceive requests, return responses, and otherwise interface with networkelements located separately from system 500.

In some embodiments, management interface 525 communicates informationvia an out-of-band connection separate from LAN and/or WAN basedcommunications, where “in-band” communications are communications thattraverse the same communication means as payload data (e.g., content)being exchanged between networked devices and where “out-of-band”communications are communications that traverse an isolatedcommunication means, separate from the mechanism for communicating thepayload data. An out-of-band connection may serve as a redundant orbackup interface over which to communicate control data between themanagement device 501 (or one of 170, 325, or 425) and other networkeddevices or between the management device 501 and a third party serviceprovider.

System 500 further includes LAN interface 530 to communicate informationvia a LAN based connection, including collecting LAN information fromwithin a LAN, reporting information and diagnostics to other entitieswithin the LAN, and for initiating instructions and commands over theLAN. Information communicated via a LAN interface 530 may, in someembodiments, traverse the LAN to a LAN to WAN interface and continue toa destination within a connected WAN. System 500 further includes WANinterface 535 to communicate information via a WAN based connection,including collecting WAN information from within a WAN, reportinginformation and diagnostics to other entities within the WAN, and forinitiating instructions and commands over the WAN. Informationcommunicated via WAN interface 535 may, in some embodiments, traversethe WAN to a WAN to LAN interface and continue to a LAN baseddestination.

System 500 further includes stored historical information 550 that maybe analyzed or referenced when conducting long term trending analysisand reporting. System 500 may further include multiple management events555, any of which may be initiated responsive to the identification ofan operational condition. For example, corrective actions, additionaldiagnostics, information probes, configuration change requests, localcommands, remote execution commands, and the like may be specified byand triggered as a management event 555. Similarly, operational reports,configuration reports, network activity reports and diagnostic reportsmay be generated and sent in accordance with stored management events555. The stored historical information 550 and the management events 555may be stored upon a hard drive, persistent data store, a database, orother storage location within system 500.

Distinct within system 500 is Management Device 501 which includescollection module 570, analysis module 575, diagnostics module 580, andimplementation module 585. Management Device 501 may be installed andconfigured in a compatible system 500 as is depicted by FIG. 5A, orprovided separately so as to operate in conjunction with appropriateimplementing logic 560 or other software.

In accordance with one embodiment, collection module 570 collectsinformation from available sources, such as LAN information and WANinformation via interfaces of system 500, including one or more ofmanagement interface 525, LAN interface 530, and/or WAN interface 535.Analysis module 575 analyzes the information retrieved via collectionmodule 570. In some embodiments, LAN information and WAN information isjointly analyzed to identify an operational condition within the LANbased on collected WAN information or identify an operational conditionwithin the WAN based on collected LAN information. Analysis module 575may further perform long term trending analysis based on storedhistorical information 550 or conduct neighborhood analysis based onaggregation data yielded from multiple separate and distinct LANs, orconduct other joint analysis based on LAN information sets receivedand/or based on WAN backhaul connection information sets received.Diagnostics module 580 may conduct specialized diagnostic routines andalgorithms in conjunction with or separately from analysis module 575.Diagnostics module 580 may conduct additional probing diagnostics toretrieve or trigger the output of additional diagnostics information forfurther analysis. Implementation module 585 implements and initiatesvarious management events 555 including generating and instantiatinginstructions for local or remote execution, generating and transmittingconfiguration change requests, generating and sending operationalreports, diagnostic reports, and configuration reports.

FIG. 5B shows a diagrammatic representation of a system 502 inaccordance with which embodiments may operate, be installed, integrated,or configured. Depicted as before are a memory 595, processor(s), bus515, a management interface 525 to communicate with system 502 includingto communicate with sub-components 591 and 590 of system 502, LANinterface 530 capable to communicate with LANs and LAN devices, WANinterface 535 capable to communicate with WANs, WAN backhaul connectionsand WAN devices, and implementing logic 560.

Traffic aggregation unit 591 and traffic de-aggregator 590 areseparately depicted within system 502. Traffic aggregation unit 591includes receiving unit 581 to receive data, packets, traffic, controlsignals and messages, and so forth. Traffic aggregation unit 591includes backhaul bonding unit 582 to bond multiple distinct WANbackhaul connections into a single logical backhaul connection. Trafficaggregation unit 591 includes data aggregation unit 583 to collect andaggregate data, packets, traffic, and so forth associated with multipledistinct connections, such as distinct LAN connections, and place theincoming data, packets, traffic, etc., onto a logical bonded backhaulconnection formed by the traffic aggregation unit 591. The data,packets, traffic, etc., once aggregated by data aggregation unit 583 aretransmitted, forwarded, or routed forward via the transmitting unit 584.

Traffic de-aggregator 590 includes receiving unit 591 to receiveincoming data, packets, traffic, etc. For example, such incoming data,packets, control packets, traffic may originate from various sourceswithin a WAN, such as from sources accessible via the Internet, and bedestined for one of the LANs communicably interfaced with the trafficde-aggregator 590. Traffic de-aggregator 590 further includes datade-aggregation unit 593 to split, separate, divide up, de-aggregateincoming data, packets, traffic etc. which is received by receiving unit591. For example, data coming into the traffic de-aggregator 590 needsto be split up and placed onto different WAN backhaul connections fortransmission back to an originating source or to a target source inaccordance with the described embodiments. Traffic de-aggregator 590further includes transmitting unit 594 to place de-aggregated data,packets, frames, etc., onto multiple WAN backhaul connections fortransmission to a specified target as described above.

FIGS. 6A, 6B, and 6C are flow diagrams 600A, 600B, and 600Crespectively, illustrating methods for traffic aggregation; methods fortraffic load balancing; and methods for self-healing in accordance withdescribed embodiments. Methods 600A, 600B, and/or 600C may be performedby processing logic that may include hardware (e.g., circuitry,dedicated logic, programmable logic, microcode, etc.), software (e.g.,instructions run on a processing device to perform various operationssuch as interfacing functions, collecting, monitoring, diagnosing andreporting information, and executing/initiating management events,commands and instructions responsive to analysis and diagnosis, or somecombination thereof). In one embodiment, methods 600A, 600B, and 600Care performed or coordinated via a Management device such as thatdepicted at element 170 of FIG. 1 or via a Management Device such asthat depicted at element 501 of FIG. 5A. Other embodiments utilize atraffic aggregation unit such as that set forth at element 225 beginningat FIG. 2A and element 591 of FIG. 5B. Still other embodiments utilize atraffic de-aggregator such as that set forth at element 235 beginning atFIG. 2B and element 590 of FIG. 5B. Some of the blocks and/or operationslisted below are optional in accordance with certain embodiments. Thenumbering of the blocks presented is for the sake of clarity and is notintended to prescribe an order of operations in which the various blocksmust occur. Additionally, operations from the various flows 600A, 600B,and 600C may be utilized in a variety of combinations.

Method 600A begins with processing logic for establishing a first LocalArea Network (LAN) via a first access device as set forth at block 602.At block 604, processing logic establishes a second LAN via a secondaccess device.

At block 606, processing logic provides the first LAN access device withWAN connectivity via a first Wide Area Network (WAN) backhaul connectionand at block 608, processing logic provides the second LAN access devicewith WAN connectivity via a second WAN backhaul connection.

At block 610, processing logic communicatively interfaces a trafficaggregation unit.

At block 612, processing logic forms a logically bonded WAN interfaceover the first WAN backhaul and the second WAN backhaul.

At block 614, processing logic combines traffic from differentconnections into aggregated traffic.

At block 616, processing logic communicatively interfaces a trafficde-aggregator.

At block 618, processing logic bonds Internet Protocol (IP) addressesassociated with traffic originating from both the first LAN and thesecond LAN.

At block 620, processing logic routes the traffic having the bonded IPaddresses through the traffic de-aggregator.

At block 622, processing logic provides an alternate backupcommunications path to the logically bonded WAN interface responsive toa failure event.

Method 600B begins with processing logic for establishing a first LocalArea Network (LAN) via a first access device as set forth at block 640.At block 642, processing logic establishes a second LAN via a secondaccess device.

At block 644, processing logic provides the first LAN access device withWAN connectivity via a first Wide Area Network (WAN) backhaul connectionand at block 646, processing logic provides the second LAN access devicewith WAN connectivity via a second WAN backhaul connection.

At block 648, processing logic communicatively interfaces a managementdevice.

At block 650, processing logic routes a first portion of trafficoriginating from the first LAN over the first WAN backhaul connection.

At block 652, processing logic routes a second portion of the trafficoriginating from the first LAN over the second WAN backhaul connection.

At block 654, processing logic implements load-balancing for the firstLAN or the second LAN or both.

At block 656, processing logic implements an aggregate transfer rate forWAN connectivity which is greater than a transfer rate for the first orsecond WAN backhaul connections individually.

At block 658, processing logic allocates a portion of bandwidthassociated with the second WAN backhaul connection to the first LANaccess device.

At block 660, processing logic instructs a first LAN device to route orswitch the second portion of traffic over a wireless communications linkfrom the first LAN access device to the second LAN access device andonto the second WAN backhaul connection.

At block 662, processing logic collects information about the first andsecond WAN backhaul connections and the first and second LANs.

At block 664, processing logic jointly analyzes the collectedinformation to identify an operational condition.

At block 666, processing logic initiates a management event responsiveto the operational condition being identified.

At block 668, processing logic generates instructions specifying aconfiguration change to a network element responsive to the operationalcondition.

Method 600C begins with processing logic for establishing a first LocalArea Network (LAN) via a first access device as set forth at block 680.At block 682, processing logic establishes a second LAN via a secondaccess device.

At block 684, processing logic provides the first LAN access device withWAN connectivity via a first Wide Area Network (WAN) backhaul connectionand at block 686, processing logic provides the second LAN access devicewith WAN connectivity via a second WAN backhaul connection.

At block 688, processing logic communicatively interfaces a managementdevice.

At block 690, processing logic implements the management device fromwithin the first LAN access device, from within a WAN access device,from within an externally separate and physically distinct deviceseparate from the LAN access device and the WAN access device, or fromwithin a service provider, and operates the management device therefrom.

At block 692, processing logic re-routes traffic responsive to a failureevent.

At block 694, processing logic performs a SONET or SDH compatible rapidre-route function.

At block 696, processing logic performs a first traffic re-routeoperation responsive to a hard failure event characterized by a totalloss of connectivity.

At block 698, processing logic performs a second traffic re-routeoperation responsive to a soft failure event characterized by degradedconnectivity.

FIG. 7 illustrates a diagrammatic representation of a machine 700 in theexemplary form of a computer system, in accordance with one embodiment,within which a set of instructions, for causing the machine 700 toperform any one or more of the methodologies discussed herein, may beexecuted. In alternative embodiments, the machine may be connected(e.g., networked) to other machines in a Local Area Network (LAN), aWide Area Network, an intranet, an extranet, or the Internet. Themachine may operate in the capacity of a server or a client machine in aclient-server network environment, or as a peer machine in apeer-to-peer (or distributed) network environment. Certain embodimentsof the machine may be in the form of a personal computer (PC), a tabletPC, a set-top box (STB), a Personal Digital Assistant (PDA), a cellulartelephone, a web appliance, a server, a network router, switch orbridge, computing system, or any machine capable of executing a set ofinstructions (sequential or otherwise) that specify actions to be takenby that machine. Further, while only a single machine is illustrated,the term “machine” shall also be taken to include any collection ofmachines (e.g., computers) that individually or jointly execute a set(or multiple sets) of instructions to perform any one or more of themethodologies discussed herein.

The exemplary computer system 700 includes a processor 702, a mainmemory 704 (e.g., read-only memory (ROM), flash memory, dynamic randomaccess memory (DRAM) such as synchronous DRAM (SDRAM) or Rambus DRAM(RDRAM), etc., static memory such as flash memory, static random accessmemory (SRAM), volatile but high-data rate RAM, etc.), and a secondarymemory 718 (e.g., a persistent storage device including hard disk drivesand persistent data base implementations), which communicate with eachother via a bus 730. Main memory 704 includes information andinstructions and software program components necessary for performingand executing the functions with respect to the various embodiments ofthe Management Device, the traffic aggregation unit, and/or the trafficde-aggregator as described herein. For example, historical WAN/LANinformation 724 may be collected LAN information from a LAN and WANinformation from a LAN which may be collected over a period of time andreferenced later for performing trending analysis. Management events maybe initiated based on historical WAN/LAN information 724. Operationalconditions may be derived from historical WAN/LAN information 724. Suchhistorical WAN/LAN information 724 may include various information sets,such as those collected from LANs, WANs, or WAN backhaul connections,historical WAN/LAN information 724 may include neighborhood analysis,and so forth. Management events 723 may be stored within main memory 704and as collected and determined by management device 734. Main memory704 and its sub-elements (e.g. 723 and 724) are operable in conjunctionwith processing logic 726 and/or software 722 and processor 702 toperform the methodologies discussed herein.

Processor 702 represents one or more general-purpose processing devicessuch as a microprocessor, central processing unit, or the like. Moreparticularly, the processor 702 may be a complex instruction setcomputing (CISC) microprocessor, reduced instruction set computing(RISC) microprocessor, very long instruction word (VLIW) microprocessor,processor implementing other instruction sets, or processorsimplementing a combination of instruction sets. Processor 702 may alsobe one or more special-purpose processing devices such as an applicationspecific integrated circuit (ASIC), a field programmable gate array(FPGA), a digital signal processor (DSP), network processor, or thelike. Processor 702 is configured to execute the processing logic 726for performing the operations and functionality which is discussedherein.

The computer system 700 may further include one or more networkinterface cards 708 to communicatively interface the computer system 700with one or more networks 720 from which information may be collectedfor analysis. The computer system 700 also may include a user interface710 (such as a video display unit, a liquid crystal display (LCD), or acathode ray tube (CRT)), an alphanumeric input device 712 (e.g., akeyboard), a cursor control device 714 (e.g., a mouse), and a signalgeneration device 716 (e.g., an integrated speaker). The computer system700 may further include peripheral device 736 (e.g., wireless or wiredcommunication devices, memory devices, storage devices, audio processingdevices, video processing devices, etc.). The computer system 700 mayperform the functions of a Management Device 734 capable interfacingnetworks, monitoring, collecting, analyzing, and reporting information,and initiating, triggering, and executing various management eventsincluding the execution of commands and instructions to alter anidentified operational condition or perform corrective measures on adiagnosed fault, as well as the various other functions and operationsdescribed herein. Data aggregation unit 735 implements data aggregationoperations, such as collecting and combining data, traffic, frames,packets, etc., which are associated with a source, such as a LAN deviceor a LAN node. Data de-aggregator 733 implements data de-aggregationoperations, such as collecting and splitting, dividing, separating,etc., data, traffic, frames, packets, and so forth from a source whichis destined for a target, such as a node or device within a connectedLAN.

The secondary memory 718 may include a non-transitory machine-readablestorage medium (or more specifically a non-transitory machine-accessiblestorage medium) 731 on which is stored one or more sets of instructions(e.g., software 722) embodying any one or more of the methodologies orfunctions described herein. Software 722 may also reside, oralternatively reside within main memory 704, and may further residecompletely or at least partially within the processor 702 duringexecution thereof by the computer system 700, the main memory 704 andthe processor 702 also constituting machine-readable storage media. Thesoftware 722 may further be transmitted or received over a network 720via the network interface card 708.

While the subject matter disclosed herein has been described by way ofexample and in terms of the specific embodiments, it is to be understoodthat the claimed embodiments are not limited to the explicitlyenumerated embodiments disclosed. To the contrary, the disclosure isintended to cover various modifications and similar arrangements aswould be apparent to those skilled in the art. Therefore, the scope ofthe appended claims should be accorded the broadest interpretation so asto encompass all such modifications and similar arrangements. It is tobe understood that the above description is intended to be illustrative,and not restrictive. Many other embodiments will be apparent to those ofskill in the art upon reading and understanding the above description.The scope of the disclosed subject matter is therefore to be determinedin reference to the appended claims, along with the full scope ofequivalents to which such claims are entitled.

1. A network manager comprising: a first interface that couples to afirst local area network (“LAN”) access device; a second interface thatcouples to a first wide area network (“WAN”) backhaul; and a thirdinterface that couples to a second WAN backhaul; wherein the networkmanager load-balances traffic from the first LAN access device such thata first portion of traffic from the first LAN access device is directedto the first WAN backhaul and a second portion of traffic from the firstLAN access device is directed to the second WAN backhaul.
 2. The networkmanager of claim 1 wherein the first interface, the second interface andthe third interface comprise at least one interface type selected from agroup consisting of logical, wireless, wired, software, or hardwareinterfaces.
 3. The network manager of claim 1 further comprising afourth interface that couples to a second LAN access device wherein thefourth interface comprise at least one interface type selected from agroup consisting of logical, wireless, wired, software, or hardwareinterfaces.
 4. The network manager of claim 3 wherein the first LANaccess device is in a first LAN and the second LAN access device is in asecond LAN.
 5. The network manager of claim 4 wherein the first LAN andthe second LAN are operationally distinct.
 6. The network manager ofclaim 3 wherein the first LAN access device and the second LAN accessdevice are connected.
 7. The network manager of claim 3 wherein thefirst LAN access device and the second LAN access device are in thefirst LAN.
 8. The network manager of claim 1 wherein the network manageris a hardware or software component within the first LAN access device.9. The network manager of claim 1 wherein the first LAN access device isselected from the group of access devices consisting of: an accesspoint; a wireless LAN access point; a modem; a router; a gateway; aDigital Subscriber Line (DSL) Customer Premises Equipment (CPE) modem orgateway; a cable modem or gateway; an IEEE P1901 standards compatibleaccess Broadband over Power Line (BPL) device; an Ethernet gateway; anEthernet connected computer peripheral device; an Ethernet connectedrouter; an Ethernet connected wireless bridge; an Ethernet connectednetwork bridge; an Ethernet connected network switch. a G.hn compatibledevice; a HomePlug device; a Home Phoneline Network Alliance (HPNA)based device; an in-home coax distribution device; an in-home power linedevice; an in-home metering communication device; an in-home applianceinterfaced with the LAN; a set-top box (STB)/set-top unit (STU) customerelectronics device; a cellular base station; a wireless femtocell basestation; a wireless compatible base station; a wireless mobile devicerepeater; a wireless mobile device base station; a network connectioncapable television; a network connection capable media player; a networkconnection capable gaming console; a network connection capable audiodevice; a network connection capable streaming device; a smartphone; apersonal computer; a laptop computer; a tablet computing device; acomputing device connected to the LAN; a network attached storagedevice; and an autonomous device;
 10. The network manager of claim 1wherein the first WAN backhaul is operationally distinct from the secondWAN backhaul.
 11. The network manager of claim 1 wherein the networkmanager directs traffic from the first LAN access device to the firstWAN backhaul when there is a failure condition in the second WANbackhaul.
 12. The network manager of claim 4 wherein the network managerdirects traffic from the first LAN access device to the first WANbackhaul when there is a failure condition in one or more of the secondWAN backhaul, the second LAN, and the second LAN access device.
 13. Anetwork manager comprising: a first interface that couples to a firstlocal area network (“LAN”) device; a second interface that couples to afirst wide area network (“WAN”) backhaul; and a third interface thatcouples to a second WAN backhaul; wherein the network managerload-balances traffic from the first LAN device such that a firstportion of traffic from the first LAN device is directed to the firstWAN backhaul and a second portion of traffic from the first LAN deviceis directed to the second WAN backhaul.
 14. The network manager of claim13 wherein the first interface, the second interface and the thirdinterface comprise at least one interface type selected from a groupconsisting of logical, wireless, wired, software, or hardwareinterfaces.
 15. The network manager of claim 13 further comprising afourth interface that couples to a second LAN device wherein the secondLAN device couples to a second LAN.
 16. The network manager of claim 13wherein the network manager is a hardware or software component withinthe first LAN device.
 17. The network manager of claim 13 wherein thefirst LAN device is selected from a group of devices consisting of: asmartphone; a personal computer; a laptop computer; a tablet computingdevice; a connected home device; a network attached storage device; anetwork connection capable portable electronic device; a networkconnection capable printer; a network connection capable digital cameraa network connection capable television; a network connection capabledisplay device; a network connection capable audio device a networkconnection capable streaming device; a network connection capable mediaplayer; a network connection capable gaming console; a networkconnection capable in-home entertainment device; a network connectioncapable in-home appliance; a network connection capable in-home device;a network connection capable in-vehicle device; and an autonomousdevice.
 18. A method for load-balancing traffic from at least one localarea network (LAN) across a plurality of wide area network (WAN)backhauls, the method comprising: receiving traffic from a first LAN;directing a first portion of received traffic from the first LAN to afirst WAN backhaul; and directing a second portion of the receivedtraffic from the first LAN to a second WAN backhaul.
 19. The method ofclaim 18 wherein the steps of directing the first portion of thereceived traffic and directing the second portion of the receivedtraffic are performed within a first LAN access device.
 20. The methodof claim 18 wherein the steps of directing the first portion of thereceived traffic and directing the second portion of the receivedtraffic is performed within a first LAN device.
 21. The method of claim18 wherein the first portion of traffic is directed to the first WANbackhaul at a rate that is less than a potential maximum transfer rateof the connection between the first LAN and the first WAN backhaul. 22.The method of claim 18 wherein traffic from the first LAN is directedentirely to the first WAN backhaul when there is a failure condition inthe second WAN backhaul.
 23. The method of claim 18 further comprisingthe steps of: receiving traffic from a second LAN that is operationallydistinct from the first LAN; directing a first portion of receivedtraffic from the second LAN to the first WAN backhaul; and directing asecond portion of the received traffic from the second LAN to the secondWAN backhaul.
 24. A network manager comprising: a first interface thatcouples to a cellular wireless base station coupled to a first wide areanetwork (WAN) backhaul; and a second interface that couples with a Wi-Fiaccess point (AP) coupled to a second WAN backhaul; wherein the networkmanager load balances traffic received from at least one LAN devicewithin the Wi-Fi local area network or the cellular wireless networksuch that a first portion of the traffic is directed to the first WANbackhaul and a second portion of the traffic is directed to the secondWAN backhaul.
 25. The network manager of claim 24 wherein the firstinterface and the second interface comprise at least one interface typeselected from a group consisting of logical, wireless, wired, software,or hardware interfaces.
 26. The network manager of claim 24 wherein thenetwork manager is integrated within a LAN device, such as a smartphone,a tablet computing device, or a Wi-Fi and cellular enabled electronicdevice.
 27. The network manager of claim 24 wherein the network manageris integrated within the Wi-Fi access point or the cellular basestation.
 28. The network manager of claim 24 wherein the network managerdirects the traffic received from the LAN device to the second WANbackhaul when there is a failure condition in one or more of: the firstWAN backhaul, the cellular access network, and the cellular basestation, and the network manager directs the traffic received from theLAN device to the first WAN when there is a failure condition in one ormore of: the second WAN backhaul, the Wi-Fi network, and the Wi-Fiaccess point.
 29. The network manager of claim 24 wherein the secondportion of the traffic is further directed to the cellular wireless basestation.
 30. The network manager of claim 24 wherein the network manageris integrated within a cellular base station controller, or a cellularpacket gateway.